Created attachment 1718188 [details] importer-pod-log Description of problem: Importing specific registry images from quay.io fails Version-Release number of selected component (if applicable): 2.5.0 How reproducible: 100% Steps to Reproduce: 1. Create DV that imports from registry (specific image described below) 2. 3. Actual results: Import stuck in "ImportInProgress" with errors in importer pod log Expected results: Import successful Additional info: 2.5.0 -> Fails 2.4.1 -> Same image gets imported successfully Importer log attached [cnv-qe-jenkins@akalenyu251-8hn8j-executor registry-fails-2.5]$ cat dv_public.yaml apiVersion: cdi.kubevirt.io/v1beta1 kind: DataVolume metadata: name: import-registry-quay-dv spec: source: registry: url: docker://quay.io/kubevirt/cirros-registry-disk-demo pvc: accessModes: - ReadWriteOnce resources: requests: storage: 5Gi storageClassName: hostpath-provisioner volumeMode: Filesystem contentType: kubevirt
This image's layers have `MediaType` field empty.
Verified on CNV 2.5.0, KubeVirt: v0.34.0-13-g2cc7d61, CDI: Containerized Data Importer v1.23.6 HCO-v2.5.0-329 HCO image: registry.redhat.io/container-native-virtualization/hyperconverged-cluster-operator@sha256:631d9868743d52fba5fb5a089acc418328e0c33c55ae2319e5e06c24a4323124 CSV creation time: 2020-10-11 19:19:07
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Virtualization 2.5.0 Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:5127