-
Bug
-
Resolution: Unresolved
-
Minor
-
Logging 6.4.0
-
Quality / Stability / Reliability
-
1
-
False
-
-
False
-
NEW
-
NEW
-
-
-
Logging - Sprint 278
Description of problem: When LokiStack components are provisioned with an incorrect storage class, the components are in pending state as expected but the alert 'LokistackComponentsNotReadyWarning' is not firing.
$ oc get pods -n openshift-logging
NAME READY STATUS RESTARTS AGE
cluster-logging-operator-746c96646d-lr5w2 1/1 Running 0 3h56m
logging-clf-2nw9w 1/1 Running 0 3h54m
logging-clf-7nl76 1/1 Running 0 3h54m
logging-clf-d6zh6 1/1 Running 0 3h54m
logging-clf-ddhvz 1/1 Running 0 3h54m
logging-clf-tcd6x 1/1 Running 0 3h54m
logging-clf-vjjd7 1/1 Running 0 3h54m
logging-loki-compactor-0 0/1 Pending 0 109m
logging-loki-distributor-7844dcf4c-27f9x 1/1 Running 0 109m
logging-loki-gateway-ffb9bcf99-ljrn4 2/2 Running 0 109m
logging-loki-gateway-ffb9bcf99-zw686 2/2 Running 0 109m
logging-loki-index-gateway-0 0/1 Pending 0 109m
logging-loki-ingester-0 0/1 Pending 0 109m
logging-loki-querier-699cdd64d5-g5m5j 1/1 Running 0 109m
logging-loki-query-frontend-697789794b-hkkww 1/1 Running 0 109m
logging-loki-ruler-0 0/1 Pending 0 109m
Version-Release number of selected component (if applicable): Logging 6.4
How reproducible: Always
Steps to Reproduce:
a) Deploy Loki Operator 6.4
b) Create LokiStack with a wrong storage class to make components in pending status.
Actual results: LokistackComponentsNotReadyWarning does not fire.
Expected results: LokistackComponentsNotReadyWarning should be firing.
Additional Info:
The alert LokistackComponentsNotReadyWarning can be seen firing when ingester is not ready (for e.g. Create LokiStack with correct storage class but incorrect object storage bucket name in secret).
