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

Image Registry default to Removed on IBM cloud after 4.13.0-ec.3

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 4.13.0
    • 4.13
    • Image Registry
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Bug Fix
    • Done

      This is a clone of issue OCPBUGS-8224. The following is the description of the original issue:

      Description of problem:

      When install a cluster on IBM cloud, the image registry default to Removed, no storage configured after 4.13.0-ec.3
      Image registry should use ibmcos object storage on IPI-IBM cluster 
      https://github.com/openshift/cluster-image-registry-operator/blob/master/pkg/storage/storage.go#L182 

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

      4.13.0-0.nightly-2023-02-27-101545

      How reproducible:

      always

      Steps to Reproduce:

      1.Install an IPI cluster on IBM cloud
      2.Check image registry after install successfully
      3.
      

      Actual results:

      oc get config.image/cluster -o yaml 
        spec:
          logLevel: Normal
          managementState: Removed
          observedConfig: null
          operatorLogLevel: Normal
          proxy: {}
          replicas: 1
          requests:
            read:
              maxWaitInQueue: 0s
            write:
              maxWaitInQueue: 0s
          rolloutStrategy: RollingUpdate
          storage: {}
          unsupportedConfigOverrides: null
      oc get infrastructure cluster -o yaml
      apiVersion: config.openshift.io/v1
      kind: Infrastructure
      metadata:
        creationTimestamp: "2023-03-02T02:21:06Z"
        generation: 1
        name: cluster
        resourceVersion: "531"
        uid: 8d61a1e2-3852-40a2-bf5d-b7f9c92cda7b
      spec:
        cloudConfig:
          key: config
          name: cloud-provider-config
        platformSpec:
          type: IBMCloud
      status:
        apiServerInternalURI: https://api-int.wxjibm32.ibmcloud.qe.devcluster.openshift.com:6443
        apiServerURL: https://api.wxjibm32.ibmcloud.qe.devcluster.openshift.com:6443
        controlPlaneTopology: HighlyAvailable
        etcdDiscoveryDomain: ""
        infrastructureName: wxjibm32-lmqh7
        infrastructureTopology: HighlyAvailable
        platform: IBMCloud
        platformStatus:
          ibmcloud:
            cisInstanceCRN: 'crn:v1:bluemix:public:internet-svcs:global:a/fdc2e14cf8bc4d53a67f972dc2e2c861:e8ee6ca1-4b31-4307-8190-e67f6925f83b::'
            location: eu-gb
            providerType: VPC
            resourceGroupName: wxjibm32-lmqh7
          type: IBMCloud 

      Expected results:

      Image registry should use ibmcos object storage on IPI-IBM cluster 

      Additional info:

      Must-gather log https://drive.google.com/file/d/1N-WUOZLRjlXcZI0t2O6MXsxwnsVPDCGQ/view?usp=share_link 

              fmissi Flavian Missi
              openshift-crt-jira-prow OpenShift Prow Bot
              XiuJuan Wang XiuJuan Wang
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: