You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
obo-prometheus-operator Failed to watch *v1.Secret: failed to list *v1.Secret: stream error when reading response body, may be caused by closed connection.
#275
Open
msk-kiratech opened this issue
Apr 20, 2023
· 0 comments
We are following this upgrade plan for an Openshift Cluster:
from version 4.10.13 to 4.10.55,
from 4.10.55 to 4.11.34,
from 4.11.34 from to 4.12.10.
All steps are currently completed.
However the obo-prometheus-operator pod seems to keep restarting.
In the attachment, you can find the current log of the component obo-prometheus-operator.txt . The operator is not connecting to another component, keeps failing and finally it restarts. This problem occurs again after the restarts.
The image of the pod is: quay.io/rhobs/obo-prometheus-operator:v0.61.1-rhobs1
Can you please check the log file and provide a solution for this issue?
Thank you
Best Regards,
MSP Kiratech
The text was updated successfully, but these errors were encountered:
Hi,
We are following this upgrade plan for an Openshift Cluster:
All steps are currently completed.
However the obo-prometheus-operator pod seems to keep restarting.
In the attachment, you can find the current log of the component obo-prometheus-operator.txt . The operator is not connecting to another component, keeps failing and finally it restarts. This problem occurs again after the restarts.
The image of the pod is: quay.io/rhobs/obo-prometheus-operator:v0.61.1-rhobs1
Can you please check the log file and provide a solution for this issue?
Thank you
Best Regards,
MSP Kiratech
The text was updated successfully, but these errors were encountered: