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

[loki-operator] Deleting LokiStack does not propagate to resources after 5.5 update

    XMLWordPrintable

Details

    • False
    • None
    • False
    • NEW
    • VERIFIED
    • Before this update, resources created by a prior version of the Loki Operator remained after upgrading to 5.5. With this update, upgrading the Operator cleans up resources correctly.
    • Log Storage - Sprint 223, Log Storage - Sprint 224, Log Storage - Sprint 225

    Description

      After updating loki-operator from 5.4 to 5.5 deleting a LokiStack resources will not cause the created resources to be deleted as well.

      The cause of this is that the ownerReferences attribute of the dependent resources still contains a reference to the v1beta1 instance of the LokiStack resource, which is not available anymore after the upgrade to loki-operator 5.5

      Attachments

        Issue Links

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: LOG

              People

                rojacob@redhat.com Robert Jacob
                rojacob@redhat.com Robert Jacob
                Kabir Bharti Kabir Bharti
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: