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

TALM does not enforce subscriptions when catalogsource is updated and both policies are in the same CGU

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • None
    • 4.12
    • TALM Operator
    • None
    • CNF RAN Sprint 231, CNF RAN Sprint 232, CNF RAN Sprint 233, CNF RAN Sprint 234
    • 4
    • False
    • Hide

      None

      Show
      None
    • Hide
      TALM skips remediating a policy if all selected clusters are compliant when the ClusterGroupUpdate CR is started.
      The update of operators with a modified catalog source policy and a subscription policy in the same ClusterGroupUpdate CR does not complete. The subscription policy is skipped as it is still compliant until the catalog source change is enforced.
      As a workaround, add a trivial change to one CR in the common-subscription policy, for example metadata.annotations.upgrade: "1". This makes the policy non-compliant prior to the start of the ClusterGroupUpdate CR.
      Show
      TALM skips remediating a policy if all selected clusters are compliant when the ClusterGroupUpdate CR is started. The update of operators with a modified catalog source policy and a subscription policy in the same ClusterGroupUpdate CR does not complete. The subscription policy is skipped as it is still compliant until the catalog source change is enforced. As a workaround, add a trivial change to one CR in the common-subscription policy, for example metadata.annotations.upgrade: "1". This makes the policy non-compliant prior to the start of the ClusterGroupUpdate CR.
    • Known Issue
    • In Progress
    • Rel Note for Telco: Yes

      In the reference configuration the CatalogSource is in the common-config policy and subscriptions are in common-subscriptions. If the user updates the catalogsource to point to a new index (as recommended) and places both common-config and common-subscriptions into the CGU for enforcement, only the common-config policy is enforced.

      TALM sees that the common-subscription Policy starts off as Compliant (it won't go non-compliant until the index is changed) and skips enforcement of the Policy.

      The workaround is to add a trivial change to one CR in the common-subscription policy. This will set the policy to non-compliant prior to the CGU being enabled and keep TALM from skipping it. For example (the value can be changed on each upgrade as needed):

          - fileName: SriovSubscription.yaml
            policyName: "subscriptions-policy"
            metadata:
              annotations:
                temp-for-upgrade: "1"

            bblock@redhat.com Bonnie Block
            rhn-support-imiller Ian Miller
            Bonnie Block Bonnie Block
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: