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

"Could not start a watch request" error when using OperatorPolicy

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • ACM 2.10.4
    • ACM 2.10.3
    • GRC
    • None
    • 1
    • False
    • None
    • False
    • GRC Sprint 2024-13
    • -
    • No

      Description of problem:

      Trying to create an OperatorPolicy it fails with 

      E0624 07:16:10.354006 1 client.go:633] Could not start a watch request for policy.open-cluster-management.io/v1beta1, Kind=OperatorPolicy, Namespace=, Name=group-sync-operator, Selector=, error: operatorpolicies.policy.open-cluster-management.io "group-sync-operator" is forbidden: User "system:serviceaccount:open-cluster-management-agent-addon:governance-policy-framework-sa" cannot list resource "operatorpolicies" in API group "policy.open-cluster-management.io" at the cluster scope 2024-06-24T07:16:10.354Z info controller/controller.go:115 Observed a panic in reconciler: close of closed channel {"controller": "policy-template-sync", "controllerGroup": "policy.open-cluster-management.io", "controllerKind": "Policy", "Policy":

      {"name":"group-sync-operator","namespace":"ocpprod"}

      , "namespace": "ocpprod", "name": "group-sync-operator", "reconcileID": "7e252a04-648b-48f4-990c-8bd6d26d7775"} panic: close of closed channel [recovered] panic: close of closed channel goroutine 418 [running]: sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile.func1() /remote-source/deps/gomod/pkg/mod/sigs.k8s.io/controller-runtime@v0.16.3/pkg/internal/controller/controller.go:116 +0x1e5 panic({0x1bf4500?, 0x21b2030?}) /usr/lib/golang/src/runtime/panic.go:914 +0x21f k8s.io/client-go/tools/watch.(*RetryWatcher).Stop(0x1bd5a40?)

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

      2.10

      How reproducible:

      Steps to Reproduce:

      1. Create a policy that has a dependency on an OperatorPolicy without specifying a namespace
      2. Check the governance-policy-framework to see if it crashes

      Actual results:

      Expected results:

      Additional info:

              mprahl Matthew Prahl
              rhn-support-afaulhab Anne Faulhaber
              Derek Ho Derek Ho
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: