-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.16.0
-
Moderate
-
No
-
Approved
-
False
-
-
N/A - fixed in same version as introduced issue
-
Release Note Not Required
-
In Progress
Description of problem:
After build02 is upgraded to 4.16.0-ec.4 from 4.16.0-ec.3, the CSRs are not auto-approved. As a result, provisioned machines cannot become nodes of the cluster.
Version-Release number of selected component (if applicable):
oc --context build02 get clusterversion version NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.16.0-ec.4 True False 4h28m
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
mimccune@redhat.com feels the group "system:serviceaccounts" was missing in the CSR.
https://redhat-internal.slack.com/archives/CBZHF4DHC/p1710875084740869?thread_ts=1710861842.471739&cid=CBZHF4DHC
An inspection of the namespace openshift-cluster-machine-approver:
https://redhat-internal.slack.com/archives/CBZHF4DHC/p1710863462860809?thread_ts=1710861842.471739&cid=CBZHF4DHC
A workaround to approve the CSRs manually on b02:
https://github.com/openshift/release/pull/50016
- is blocked by
-
MCO-1091 Impact The CRSs are not auto-approved on 4.16.0-ec.4
-
- Closed
-
- relates to
-
-
- Closed
-
- links to
-
RHEA-2024:0041
OpenShift Container Platform 4.16.z bug fix update
