Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-25330

catalog-operator is checking on any namespace instead of just checking the ones that do have a subscription

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • None
    • 4.14
    • OLM
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * In Operator Lifecycle Manager (OLM), the Catalog Operator was logging many errors regarding missing `OperatorGroup` objects in namespaces that had no Operators installed. With this fix, if a namespace has no `Subscription` objects in it, OLM no longer checks if an `OperatorGroup` object is present in the namespace. (link:https://issues.redhat.com/browse/OCPBUGS-25330[*OCPBUGS-25330*])
      Show
      * In Operator Lifecycle Manager (OLM), the Catalog Operator was logging many errors regarding missing `OperatorGroup` objects in namespaces that had no Operators installed. With this fix, if a namespace has no `Subscription` objects in it, OLM no longer checks if an `OperatorGroup` object is present in the namespace. (link: https://issues.redhat.com/browse/OCPBUGS-25330 [* OCPBUGS-25330 *])
    • Bug Fix
    • Done

      Description of problem:

      In OCP 4.14, there are many logs in catalog-operator pod:
      ~~~~~~~~~~~~~~~~
      E1213 10:17:15.519754       1 queueinformer_operator.go:319] sync {"update" "openshift-network-node-identity"} failed: found 0 operatorGroups, expected 1
      E1213 10:17:15.718852       1 queueinformer_operator.go:319] sync {"update" "openshift-apiserver-operator"} failed: found 0 operatorGroups, expected 1
      E1213 10:17:15.920209       1 queueinformer_operator.go:319] sync {"update" "openshift-authentication-operator"} failed: found 0 operatorGroups, expected 1
      E1213 10:17:16.120160       1 queueinformer_operator.go:319] sync {"update" "openshift-kube-controller-manager-operator"} failed: found 0 operatorGroups, expected 1
      E1213 10:17:16.319978       1 queueinformer_operator.go:319] sync {"update" "openshift-cloud-network-config-controller"} failed: found 0 operatorGroups, expected 1
      ~~~~~~~~~~~~~~~~
      
       It looks like catalog-operator is checking on any namespace instead of just checking the ones that do have a subscription
      
      This behavior is not seen in OCP 4.12, 4.13.

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

          

      How reproducible:

          

      Steps to Reproduce:

          1. Install the operator
          2. See the logs of catalog-operator
      ~~~
      $ oc project openshift-operator-lifecycle-manager
      $ oc logs catalog-operator-xxxxxx-xxxxx
      
      E1213 10:17:46.719417       1 queueinformer_operator.go:319] sync {"update" "openshift-etcd-operator"} failed: found 0 operatorGroups, expected 1
      E1213 10:17:46.919541       1 queueinformer_operator.go:319] sync {"update" "openshift-ingress"} failed: found 0 operatorGroups, expected 1
      E1213 10:17:47.119342       1 queueinformer_operator.go:319] sync {"update" "openshift-kube-scheduler"} failed: found 0 operatorGroups, expected 1
      E1213 10:17:47.319892       1 queueinformer_operator.go:319] sync {"update" "openshift-apiserver"} failed: found 0 operatorGroups, expected 1
      E1213 10:17:47.519461       1 queueinformer_operator.go:319] sync {"update" "openshift-authentication"} failed: found 0 operatorGroups, expected 1
      E1213 10:17:47.719498       1 queueinformer_operator.go:319] sync {"update" "openshift-cluster-samples-operator"} failed: found 0 operatorGroups, expected 1 
      ~~~    

      Actual results:

      - catalog-operator producing lots of messages like above.
      - Need to understand the reason

      Expected results:

      - catalog-operator should not produce this much logs like above.
      - Need to understand the reason.

      Additional info:

          

            agreene1991 Alexander Greene
            rhn-support-duge Dushyant Uge
            Xia Zhao Xia Zhao
            Alex Dellapenta Alex Dellapenta
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: