-
Notifications
You must be signed in to change notification settings - Fork 306
20% of the openstack-cinder-csi-driver-controller-metrics is down #2126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Are you still experiencing this issue? |
Yes, it has not stopped firing since and the container still logs the error. |
My understanding is that the signing keys were fixed in 4.18.0-okd-scos.8. With regards to your reported issue, I have found a similar report here: https://issues.redhat.com/browse/OCPBUGS-54975 Does this seem to match? It has an open PR here but has not yet been merged openshift/csi-operator#379 |
Yes, it is the same issue and as for the upgrade issue, we will wait until there is an official upgrade path. |
Can confirm the same behavior in 4.18.scos.8 and 4.18.scos.9 |
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
The
openstack-cinder-csi-driver-controller-metrics.openshift-cluster-csi-drivers.svc:9202/metrics
endpoint requested by theopenstack-cinder-csi-driver-controller-monitor
service monitor is down since upgrading from4.18.0-okd-scos.2
to4.18.0-okd-scos.4
. It seems that thecsi-driver
container of theopenstack-cinder-csi-driver-controller
deployment does not listen on the port 8202 as requested by thekube-rbac-proxy-8202
(which provides the metrics endpoint). The logs of thekube-rbac-proxy-8202
container contain the following log:Version
4.18.0-okd-scos.4
IPI on OpenStackHow reproducible
The issue is reproducible on our staging and production cluster.
TargetDown
alert firing sinceThe text was updated successfully, but these errors were encountered: