-
Bug
-
Resolution: Done-Errata
-
Undefined
-
4.15.z, 4.16.0
-
None
-
Critical
-
No
-
False
-
-
Release Note Not Required
-
In Progress
Description of problem:
In the tested HCP external OIDC env, when issuerCertificateAuthority is set, console pods are stuck in ContainerCreating status. The reason is the CA configmap is not propagated to openshift-console namespace by the console operator.
Version-Release number of selected component (if applicable):
Latest 4.16 and 4.15 nightly payloads
How reproducible:
Always
Steps to Reproduce:
1. Configure HCP external OIDC env with issuerCertificateAuthority set. 2. Check oc get pods -A
Actual results:
2. Before OCPBUGS-31319 is fixed, console pods are in CrashLoopBackOff status. After OCPBUGS-31319 is fixed or manually coping the CA configmap to openshift-config namespace as workaround, console pods are stuck in ContainerCreating status until the CA configmap is manually copied to openshift-console namespace too. Console login is affected.
Expected results:
2. Console operator should be responsible to copy the CA to openshift-console namespace. And console login should succeed.
Additional info:
In https://redhat-internal.slack.com/archives/C060D1W96LB/p1711548626625499 , HyperShift Dev side Seth requested to create this separate console bug to unblock the PR merge and backport for OCPBUGS-31319 . So creating it
- blocks
-
-
- POST
-
- is cloned by
-
-
- POST
-
- links to
-
RHEA-2024:0041
OpenShift Container Platform 4.16.z bug fix update
