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

[4.16] Latest TALM operator bundle in all releases has CGUO and Not TALM as bundle name

XMLWordPrintable

    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • None
    • x86_64
    • Dev
    • Proposed
    • None
    • Proposed
    • Bug Fix
    • Hide
      Cause: Inconsistent labeling and a typo in the operator's background settings meant that internal labels didn't match the intended configuration.
      Consequence: This could cause the operator to fail during installation or prevent it from appearing in the correct update channels.
      Fix: The labels and configuration settings have been updated to be consistent and accurate.
      Result: Operators now install correctly and are available in the expected update channels (such as "stable").
      Show
      Cause: Inconsistent labeling and a typo in the operator's background settings meant that internal labels didn't match the intended configuration. Consequence: This could cause the operator to fail during installation or prevent it from appearing in the correct update channels. Fix: The labels and configuration settings have been updated to be consistent and accurate. Result: Operators now install correctly and are available in the expected update channels (such as "stable").
    • None
    • None
    • None
    • None

      Description of problem:

      The label `operators.operatorframework.io.bundle.package.v1` on the TALM operator bundle has an incorrect name. For the latest version in all releases, it is `cluster-group-upgrades-operator`. Previously, it was `topology-aware-lifecycle-manager`.

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

          4.12-4.22

      How reproducible:

          100%

      Steps to Reproduce:

          1.Inspect labels on TALM bundle

      Actual results:

          `cluster-group-upgrade-operators` name is present

      Expected results:

           `topology-aware-lifecycle-manager` name is present

      Additional info:

          Slack thread: https://redhat-internal.slack.com/archives/C02EG99MR9C/p1770392388015599
    Customer Ticket: https://access.redhat.com/support/cases/#/case/04370773

              sskeard@redhat.com Steven Skeard
              rhn-gps-ncocker Nabeel Cocker
              None
              None
              Kirsten Laskoski Kirsten Laskoski
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: