rhobs / rhobs/observability-operator
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.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 51
- Forks
- 90
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 22
Description
Hi,
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the attached obo-prometheus-operator log and reviewing the reported pod restart behavior across the OpenShift 4.10.13-to-4.12.10 upgrade path. Confirm the failure with image quay.io/rhobs/obo-prometheus-operator:v0.61.1-rhobs1; done means identifying the cause of the Secret watch failure and documenting a verified solution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, prometheus
- Domain
- infrastructure, observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100