Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-3496

[release-5.6] LokiStack status is still 'Pending' when all loki components are running

    XMLWordPrintable

Details

    • 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

      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

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. LOG-3430 LokiStack status is still 'Pending' when all loki components are running

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          links to

          GitHub openshift/loki#98: [release-5.6] Fix status not updating when state of pods changes

          mentioned on

          GitLab Merge request - Updated 2 upstream sources

          Activity

            People

              rojacob@redhat.com Robert Jacob
              rhn-support-kbharti Kabir Bharti
              Kabir Bharti Kabir Bharti
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: