-
Bug
-
Resolution: Done
-
Major
-
None
-
4.19
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
After the cluster is deployed in AWS UPI in 4.19 the console pods keep deploying continuously.
Version-Release number of selected component (if applicable):
4.19.9
Steps to Reproduce:
1. Create a UPI cluster on aws.
Actual results:
Continuous redeployment of console-operator.
Expected results:
The operator should not re-deploy.
Additional info:
This seems to be a similar bug which was fixed in 4.16.4 https://issues.redhat.com/browse/OCPBUGS-36588.
We find logs like: 2025-09-04T07:16:01.589070671Z E0904 07:16:01.589042 1 status.go:130] SyncLoopRefreshProgressing InProgress working toward version 4.19.9, 1 replicas available 2025-09-04T07:16:03.263118369Z E0904 07:16:03.263077 1 telemetry.go:103] telemetry config error: HTTP request failed with status '429 Too Many Requests' Field ORGANIZATION_ID in the console-config ``configmapis also continuously changing from a value to blank as per theconsole-operator` logs.
- duplicates
-
OCPBUGS-58094 console pods are frequently redeployed
-
- Verified
-