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

[loki-operator] Degraded status immediately reset when no pod actions are pending

XMLWordPrintable

    • False
    • False
    • NEW
    • OBSDA-7 - Adopting Loki as an alternative to Elasticsearch to support more lightweight, easier to manage/operate storage scenarios
    • NEW
    • Logging (LogExp) - Sprint 215, Logging (LogExp) - Sprint 216

      While testing LOG-2236 I noticed that the Degraded conditions are immediately reset to False when no additional error is emitted by handlers.CreateOrUpdateLokiStack() and there are either no deployments created by loki-operator yet or they are still "okay" as seen from the last successful reconciliation run.

      It seems this is because the last reconciliation step (status.Refresh()) is only looking at the pod statuses and not taking other error conditions into account.

              sasagarw@redhat.com Sashank Agarwal (Inactive)
              rojacob@redhat.com Robert Jacob
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: