Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-55082

kubevirt-disk-uploader uses internal image

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • CNV v4.18.0
    • None
    • CNV User Interface
    • None
    • Quality / Stability / Reliability
    • 0.42
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • None

      Description of problem:

      the kubevirt-disk-uploader pod is still created from
      image: registry-proxy.engineering.redhat.com/rh-osbs/kubevirt-tekton-tasks-create-datavolume-rhel9-container-v4.18.0-16
      But the 4.17 version of the image should work and is already published
      
      

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

      4.18
      

      How reproducible:

      100%
      

      Steps to Reproduce:

      1. Virtualization -> Bootable volumes -> Upload to registry
      2. Fill form with dummy values and Upload
      
      

      Actual results:

      Upload shows circle of death, and the related pod fails with
      Failed to pull image "registry-proxy.engineering.redhat.com/rh-osbs/kubevirt-tekton-tasks-create-datavolume-rhel9-container-v4.18.0-16": initializing source docker://registry-proxy.engineering.redhat.com/rh-osbs/kubevirt-tekton-tasks-create-datavolume-rhel9-container-v4.18.0-16:latest: pinging container registry registry-proxy.engineering.redhat.com: Get "https://registry-proxy.engineering.redhat.com/v2/": dial tcp: lookup registry-proxy.engineering.redhat.com: no such host
      
      

      Expected results:

      upload works
      

      Additional info:

              upalatuc@redhat.com Ugo Palatucci
              dholler@redhat.com Dominik Holler
              Guohua Ouyang Guohua Ouyang
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: