Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-6162

Policy/policy.open-cluster-management.io stuck in progressing status when no clusters match the policy

XMLWordPrintable

    • False
    • None
    • False
    • Hide
      Before this update, any RHACM policy (Policy/policy.open-cluster-management.io resource) would show the health check status as 'Progressing' even when there are no clusters to which the policy applies. With this update, the health check status would remain 'Healthy' when there are no clusters to which the policy applies.
      Show
      Before this update, any RHACM policy (Policy/policy.open-cluster-management.io resource) would show the health check status as 'Progressing' even when there are no clusters to which the policy applies. With this update, the health check status would remain 'Healthy' when there are no clusters to which the policy applies.
    • Bug Fix
    • Proposed

      Description of Problem

      • Describe the bug

      The newly introduced Policy/policy.open-cluster-management.io resource healthcheck is showing the Progressing state, even when a policy does not apply to any clusters. This is incorrect and it makes the whole application in Progressing state even though there is nothing to progress since the policy will never apply to any cluster.

      To Reproduce

      Just create a policy with a placementrule that does not match any existing cluster imported in ACM.
      For example: https://gist.github.com/mbaldessari/f3f090ab7fabc904d2038379f61ad312

      Expected behavior

      The policy should be in healthy state as there is nothing to do

      Additional Info

      •  

      Reproducibility

      • Always

      Prerequisites/Environment

      • OpenShift 4.14 or greater, RHACM, OpenShift GitOps 1.15

       

              isequeir@redhat.com Ishita Sequeira
              rhn-support-awyatt Albert Wyatt
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: