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

Stale condition present on CLO6 ClusterLogForwarder instance after rebooting cluster

XMLWordPrintable

    • False
    • None
    • False
    • NEW
    • NEW
    • If Release Note Needed, Set a Value
    • Hide

      1. Install CLO6
      2. Wait for install to complete
      3. Check conditions on CLF instance
      4. Reboot cluster
      5. Wait for reboot to complete
      6. Check conditions on CLF instance

      Show
      1. Install CLO6 2. Wait for install to complete 3. Check conditions on CLF instance 4. Reboot cluster 5. Wait for reboot to complete 6. Check conditions on CLF instance
    • Low

      I have this stale condition perpetually present on my cluster's ClusterLogForwarder instance after rebooting with CLO6 installed:

        {
          "lastTransitionTime": "2024-09-17T19:50:19Z",
          "message": "failed to get /logging-scc SecurityContextConstraints: failed to get restmapping: no matches for kind \"SecurityContextConstraints\" in group \"security.openshift.io\"",
          "reason": "DeploymentError",
          "status": "False",
          "type": "Ready"
        } 

      The condition appears after rebooting the cluster and does not appear to ever resolve. 

      Given the nature of a reboot being involved, I would guess this is is a race condition on how fast the node reboots versus when CLO is checking for the SCC.

              Unassigned Unassigned
              sskeard@redhat.com Steven Skeard
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: