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

OLM catalogs all use the same tag even if one particular catalog's tag is not available

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 4.19.0
    • HyperShift
    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

        Currently only the following pull refs for v4.19 OLM catalogs are available:

registry.redhat.io/redhat/certified-operators:v4.19              
registry.redhat.io/redhat/redhat-marketplace:v4.19                
registry.redhat.io/redhat/redhat-operators:v4.19  

for community operators, only the 4.18 tag is available:

registry.redhat.io/redhat/community-operators:v4.18

This causes HyperShift clusters to not run a community-operators catalog

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

          4.19

      How reproducible:

          Only under current conditions

      Steps to Reproduce:

          1. Create a 4.19 HostedCluster
    2. Wait for control plane pods to roll out

      Actual results:

          A community-operators catalog pod never comes up

      Expected results:

          All catalog pods start

      Additional info:

       

              cewong@redhat.com Cesar Wong
              cewong@redhat.com Cesar Wong
              Jie Zhao Jie Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: