-
Bug
-
Resolution: Done-Errata
-
Undefined
-
None
-
4.17
-
None
-
Critical
-
Yes
-
Proposed
-
False
-
-
N/A
-
Release Note Not Required
-
Done
Description of problem:
Checking the vsphere-problem-detector-operator log in 4.17.0-0.nightly-2024-07-28-191830, it threw the error message as below: W0729 01:36:04.693729 1 reflector.go:547] k8s.io/client-go@v0.30.2/tools/cache/reflector.go:232: failed to list *v1.ClusterCSIDriver: clustercsidrivers.operator.openshift.io is forbidden: User "system:serviceaccount:openshift-cluster-storage-operator:vsphere-problem-detector-operator" cannot list resource "clustercsidrivers" in API group "operator.openshift.io" at the cluster scope E0729 01:36:04.693816 1 reflector.go:150] k8s.io/client-go@v0.30.2/tools/cache/reflector.go:232: Failed to watch *v1.ClusterCSIDriver: failed to list *v1.ClusterCSIDriver: clustercsidrivers.operator.openshift.io is forbidden: User "system:serviceaccount:openshift-cluster-storage-operator:vsphere-problem-detector-operator" cannot list resource "clustercsidrivers" in API group "operator.openshift.io" at the cluster scope
And vsphere-problem-detector-operator continue restarting: vsphere-problem-detector-operator-76d6885898-vsww4 1/1 Running 34 (11m ago) 7h18m
It might be caused by https://github.com/openshift/vsphere-problem-detector/pull/166 and we have not added the clusterrole in openshift/cluster-storage-operator repo yet.
Version-Release number of selected component (if applicable):
4.17.0-0.nightly-2024-07-28-191830
How reproducible:
Always
Steps to Reproduce:
See Description
Actual results:
vsphere-problem-detector-operator report permission lack and restart
Expected results:
vsphere-problem-detector-operator should not report permission lack and restart
Additional info:
- links to
-
RHEA-2024:3718
OpenShift Container Platform 4.17.z bug fix update