-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
False
-
None
-
False
-
NEW
-
NEW
-
-
Bug Fix
-
-
-
-
-
Log Collection - Sprint 265
-
Low
I have this stale condition perpetually present on my cluster's ClusterLogForwarder instance after rebooting with CLO6 installed:
{ "lastTransitionTime": "2024-09-17T19:50:19Z", "message": "failed to get /logging-scc SecurityContextConstraints: failed to get restmapping: no matches for kind \"SecurityContextConstraints\" in group \"security.openshift.io\"", "reason": "DeploymentError", "status": "False", "type": "Ready" }
The condition appears after rebooting the cluster and does not appear to ever resolve.
Given the nature of a reboot being involved, I would guess this is is a race condition on how fast the node reboots versus when CLO is checking for the SCC.
- is duplicated by
-
LOG-6418 Cluster logging operator could not create SCC logging-scc
- Verified
- links to
- mentioned on