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

when using oc adm release mirror, the openshift/release/4.x.y_x86_64-x86_64-kube-virt-container are missing and not synchronized

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Undefined Undefined
    • None
    • 4.18.z
    • oc
    • None
    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

          When using oc adm release mirror to mirror OpenShift releases, there is one container missing during the uploads, the container named openshift/release/4.x.y_x86_64-4.18.2-x86_64-kube-virt-container where 4.x.y is the release being synchronized with the local registry  

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

          I tested several 4.18.z versions and they all have the same outcome

      How reproducible:

          Always

      Steps to Reproduce:

          1. create a synchronization command similar to this one :
      date ; for i in 4.18.2 ; do oc.4.18.2 adm release mirror -a ${HOME}/pull-secret.txt --from=quay.io/openshift-release-dev/ocp-release:${i}-x86_64 --to-release-image=ocpv418release.registry.local/openshift-release-dev/ocp-release:${i}-x86_64 --to=<local registry URL>/openshift-release-dev --print-mirror-instructions=idms |& tee ${HOME}/$(date +"%Y%m%d")-release-sync.${i}.txt ; sync ;done; date
      
          2. Look for kube-virt-container in output file :
      grep kube-virt-container ${HOME}/openshift/$(date +"%Y%m%d")-release-sync.${i}.txt
      => nothing is selected
      
      

      Actual results:

      no container 4.x.y-x86_64-kube-virt-container has been synchronized

      Expected results:

       4.x.y-x86_64-kube-virt-container should also be synchronized for complete synchronization process with local registry    

      Additional info:

          

              aos-workloads-staff Workloads Team Bot Account
              egoirand@redhat.com Eric Goirand
              Ying Zhou Ying Zhou
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: