-
Bug
-
Resolution: Done
-
Minor
-
Logging 5.6.0
-
False
-
None
-
False
-
NEW
-
VERIFIED
-
Before this update, Loki Operator would not retry setting the status of the LokiStack CR, which caused stale status information. With this update, status information updates will be retried on conflict.
-
-
-
Log Storage - Sprint 229, Log Storage - Sprint 230, Log Storage - Sprint 231
Description of problem:
LokiStack CR status is not updated to Ready when all loki components are up and running.
LokiStack CR: http://pastebin.test.redhat.com/1085329
Loki components:
[kbharti@cube hack]$ oc get pods -n openshift-logging NAME READY STATUS RESTARTS AGE lokistack-dev-compactor-0 1/1 Running 0 5m3s lokistack-dev-distributor-866796f564-9sqs2 1/1 Running 0 5m3s lokistack-dev-gateway-568ddf5c9-hqvhz 2/2 Running 0 5m3s lokistack-dev-index-gateway-0 1/1 Running 0 5m3s lokistack-dev-ingester-0 1/1 Running 0 5m3s lokistack-dev-querier-b89c557b5-9dh9j 1/1 Running 0 5m3s lokistack-dev-query-frontend-5cbdf746f8-d4mrz 1/1 Running 0 5m3s lokistack-dev-ruler-0 1/1 Running 0 5m3s
Don't see this issue in Log 5.5.6
CSV: loki-operator.v5.6.0
Steps to Reproduce:
1) Deploy LokiOperator v5.6.0
2) Create secret and provision LokiStack CR
Actual results: LokiStack CR status is Pending
Expected results: LokiStack CR status is Ready
How reproducible: Occurs intermittently
- clones
-
-
- Closed
-
- links to
- mentioned on
