Loading...

XML

Word

Printable

Type: Bug
Resolution: Not a Bug
Priority: Normal
Fix Version/s: None
Affects Version/s: 4.13
Component/s: oauth-apiserver
Labels:
None

Activity Type:
Quality / Stability / Reliability
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
None
Severity:
Low
Regression:
No

Target Backport Versions:
None
Target Version:
None
Release Blocker:
None
Sprint:
None

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

PX Priority Data:
PX Impact Score:

Release Note Status:
None
Release Note Type:
None
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
None

Description of problem:

After adding a custom authentication 'componentRoute' to the 'ingress.config.openshift.io' resource, the 'oauth-openshift-...' pods in the 'openshift-authentication' go into CrashLoopBackOff.

Version-Release number of selected component (if applicable):

4.13

How reproducible:

Consistently

Steps to Reproduce:

    1. Add a custom componentRoute for authentication in the ingress.config.openshift.io resource similar to the following:

---
oc edit ingress.config.openshift.io cluster
...
  componentRoutes:
  - hostname: oauth.example.com
    name: oauth-openshift
    namespace: openshift-authentication
    servingCertKeyPairSecret:
      name: oauth-ssl2
---

Actual results:

    openshift-authentication pods go into CrashLoopBackOff

Expected results:

    Custom change would successfully be rolled out to all dependent pods.

Additional info:

Assignee:: Stanislav Láznička (Inactive)

Reporter:: Luke Stanton

QA Contact:: Jianwei Hou

Need Info From:: None

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 2024/02/12 11:41 PM

Updated:: 2025/09/12 9:18 PM

Resolved:: 2024/04/12 7:32 AM