Loading...

XML

Word

Printable

Type: Bug
Resolution: Unresolved
Priority: Major
Fix Version/s: None
Affects Version/s: 4.16
Component/s: Cloud Compute / Machine CSR Approver
Labels:
- csr
- machine
- node

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

Hide

None

Show
None
Story Points:
None
Severity:
None
Regression:
None

Target Backport Versions:
None
Target Version:
None
Release Blocker:
None
Sprint:
CLOUD Sprint 273, CLOUD Sprint 274, CLOUD Sprint 275, CLOUD Sprint 276, CLOUD Sprint 277, CLOUD Sprint 278, CLOUD Sprint 279, CLOUD Sprint 280, CLOUD Sprint 281, CLOUD Sprint 282, CLOUD Sprint 283
sprint_count:
11

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

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:

    SRE received support ticket https://issues.redhat.com/browse/OHSS-43429 Cluster have numerous pending CSR. 
It has the same symptom described in https://access.redhat.com/solutions/7083331. SRE uses this workaround to resolve the issue. For newly added machinepools, all new CSRs require manual approval.

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

How reproducible:

    SRE is still not able to figure out how to reproduce the issue.
We suspect it should same as KCS https://access.redhat.com/solutions/7083331

Steps to Reproduce:

    1.
    2.
    3.

Actual results:

 Clusters require all CSRs to be manually approved

Expected results:

     CSR should be automatically approved.

Additional info:

Assignee:: Nolan Brubaker

Reporter:: Tony Kong

Need Info From:: None

Contributors:: None

QA Contact:: Zhaohua Sun

Doc Contact:: None

Votes:: 3 Vote for this issue

Watchers:: 12 Start watching this issue

Created:: 2025/06/13 2:45 AM

Updated:: 2026/01/19 3:53 PM