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

oc mirror obtains a different than expected digest for the nmstate operator.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Critical Critical
    • None
    • 4.14.z
    • oc-mirror
    • Important
    • None
    • CLID Sprint 257
    • 1
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Nmstate operator was added to the ImageSetConfiguration from an existent mirror configuration file over a disconnected registry. The operator was added from Openshift but it is failing because a missing image:
      
      --
      kind: ImageSetConfiguration
      apiVersion: mirror.openshift.io/v1alpha2
      storageConfig:
        registry:
          imageURL: registry.example.com/oc-mirror
          skipTLS: false
      mirror:
        platform:
          architectures:
            - amd64
          channels:
          - name: stable-4.12
            type: ocp
            minVersion: 4.12.39
        operators:
        - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.12
          packages:
          - name: advanced-cluster-management
          - name: multicluster-engine
            channels:
            - name: stable-2.1
            - name: stable-2.2
            - name: stable-2.3
            - name: stable-2.4
            - name: stable-2.5
            - name: stable-2.6
          - name: openshift-gitops-operator
          - name: compliance-operator
            #        - name: devworkspace-operator
          - name: kubernetes-nmstate-operator
          - name: kubevirt-hyperconverged
          - name: local-storage-operator
          - name: mcg-operator
          - name: ocs-operator
          - name: odf-csi-addons-operator
          - name: odf-operator
          - name: security-profiles-operator
          - name: cincinnati-operator
          - name: web-terminal
          - name: file-integrity-operator
          - name: container-security-operator
          - name: rhsso-operator
          - name: odr-cluster-operator
          - name: odr-hub-operator
          - name: cluster-kube-descheduler-operator
          - name: cluster-logging
          - name: submariner
          - name: topology-aware-lifecycle-manager
          - name: rhacs-operator
        additionalImages:
        - name: registry.redhat.io/ubi8/ubi:latest
        - name: registry.redhat.io/rhel8/support-tools:latest
        - name: registry.redhat.io/openshift4/ose-tools-rhel8:v4.12
        - name: registry.redhat.io/openshift4/ztp-site-generate-rhel8:v4.12
        - name: registry.redhat.io/openshift4/ose-cli:v4.12
        helm: {}
      
      
      
      Error from pod:
      Failed to pull image "registry.redhat.io/openshift4/kubernetes-nmstate-operator-bundle@sha256:cefdefeded416905fc37d33b54ab7862e01a38598c3c366e30cc2acda9a65075": rpc error: code = Unknown desc = (Mirrors also failed: [registry.example.com/openshift4/kubernetes-nmstate-operator-bundle@sha256:cefdefeded416905fc37d33b54ab7862e01a38598c3c366e30cc2acda9a65075: reading manifest sha256:cefdefeded416905fc37d33b54ab7862e01a38598c3c366e30cc2acda9a65075 in registry.example.com/openshift4/kubernetes-nmstate-operator-bundle: manifest unknown: manifest unknown]): registry.redhat.io/openshift4/kubernetes-nmstate-operator-bundle@sha256:cefdefeded416905fc37d33b54ab7862e01a38598c3c366e30cc2acda9a65075: pinging container registry registry.redhat.io: Get "https://registry.redhat.io/v2/": dial tcp 23.204.18.253:443: connect: no route to host
      
      From the oc mirror mappings resultant file, we see that the file oc mirror obtains has a different digest than the one the operator needs:
      
      registry.redhat.io/openshift4/kubernetes-nmstate-operator-bundle@sha256:5b75b5300f2d730fb19136668cf887d83b37435e87b8320aaa5e8bba8c9cd784=registry.example.com/openshift4/kubernetes-nmstate-operator-bundle:d54d2079
      
      
      The version from oc mirror we are using is the following:
      
      sh-4.4$ oc-mirror version
      WARNING: This version information is deprecated and will be replaced with the output from --short. Use --output=yaml|json to get the full version.
      Client Version: version.Info{Major:"", Minor:"", GitVersion:"4.15.0-202405220207.p0.gfc3b010.assembly.stream.el9-fc3b010", GitCommit:"fc3b010c4c7b90cfc4f93da0813042eeea83704d", GitTreeState:"clean", BuildDate:"2024-05-22T02:38:06Z", GoVersion:"go1.20.12 X:strictfipsruntime", Compiler:"gc", Platform:"linux/amd64"}
      
      

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

      sh-4.4$ oc-mirror version
      WARNING: This version information is deprecated and will be replaced with the output from --short. Use --output=yaml|json to get the full version.
      Client Version: version.Info{Major:"", Minor:"", GitVersion:"4.15.0-202405220207.p0.gfc3b010.assembly.stream.el9-fc3b010", GitCommit:"fc3b010c4c7b90cfc4f93da0813042eeea83704d", GitTreeState:"clean", BuildDate:"2024-05-22T02:38:06Z", GoVersion:"go1.20.12 X:strictfipsruntime", Compiler:"gc", Platform:"linux/amd64"}

      How reproducible:

          

      Steps to Reproduce:

          1. Use the above ImageSetConfiguration.
          2. oc-mirror using the config file.
          3. Wait for it to finish.
          

      Actual results:

      The kubernetes-nmstate-operator-bundle digest is not the one expected.    

      Expected results:

         It should obtain the cefdefeded416905fc37d33b54ab7862e01a38598c3c366e30cc2acda9a65075 digest, but it gets the 5b75b5300f2d730fb19136668cf887d83b37435e87b8320aaa5e8bba8c9cd784 digest instead.

      Additional info:

          

              luzuccar@redhat.com Luigi Mario Zuccarelli
              rhn-gps-alfredo Alfredo Pizarro
              ying zhou ying zhou
              Alfredo Pizarro
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: