Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-4712

governance policy framework not working as expected after hub restore

XMLWordPrintable

    • False
    • None
    • False
    • GRC Sprint 2023-09
    • No

      Description of problem:

      After restoring hub cluster SNO managed clusters take a long time to sync, also running oc get policies -A results in no resources found and the following warning under events:
      Events:
        Type     Reason        Age                    From                   Message
        ----     ------        ----                   ----                   -------
        Warning  FailedCreate  6m48s (x211 over 20h)  replicaset-controller  Error creating: pods "governance-policy-framework-5668585b77-" is forbidden: autoscaling.openshift.io/ManagementCPUsOverride the pod namespace "open-cluster-management-agent-addon" does not allow the workload type management
      The above error was fixed with the following:

      oc annotate ns/open-cluster-management-agent-addon workload.openshift.io/allowed=management
      namespace/open-cluster-management-agent-addon annotated 
      

      How did the Hub Cluster restore change that on the SNO. Or, could that somehow happen on a SNO when disconnected from the Hub Cluster for a while?

      Version-Release number of selected component (if applicable): 2.6.3

      How reproducible: Currently seen in customer environment

      Steps to Reproduce:

      1. Restore hub cluster and monitor SNO managed clusters
      2.  
      3. ...

      Actual results: managed clusters take a long time to sync with the hub or they have components failing with errors

       - governance-policy

       - observability

      Expected results:

      After hub restore components on managed clusters are working fully.

      Additional info:

              leyan@redhat.com Le Yang
              rhn-support-rspagnol Ryan Spagnola
              Thuy Nguyen Thuy Nguyen
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: