Description of problem:

Creating a new windows VM with driver windows-drivers-disk fails to pull image.

After creation of VM virt-launcher pod will get into Init:ErrImagePull.

$ oc get pods
NAME                                         READY   STATUS              RESTARTS   AGE
virt-launcher-rhel7-8eydouk0ge44trb1-dvcrz   1/1     Running             0          27d
virt-launcher-windows-yashm-r9fjz            0/2     Init:ErrImagePull   0          6m12s


Describing pod with give imagepull error on virtio-win disk.

$ oc describe pod virt-launcher-windows-yashm-r9fjz

  Normal   Created         39s                kubelet            Created container container-disk-binary
  Normal   Started         39s                kubelet            Started container container-disk-binary
  Warning  Failed          24s (x2 over 38s)  kubelet            Failed to pull image "registry.redhat.io/container-native-virtualization/virtio-win@sha256:326cbe461af4c34eba009b93a2a103181d90ca225f49be99d2fa152149b685ef": rpc error: code = Unknown desc = reading manifest sha256:326cbe461af4c34eba009b93a2a103181d90ca225f49be99d2fa152149b685ef in registry.redhat.io/container-native-virtualization/virtio-win: unsupported: Not Found, or unsupported. V2 schema 1 manifest digest are no longer supported for image pulls. Use the equivalent schema 2 manifest digest instead. For more information see https://access.redhat.com/articles/6138332
  Warning  Failed          24s (x2 over 38s)  kubelet            Error: ErrImagePull
  Normal   BackOff         11s (x2 over 37s)  kubelet            Back-off pulling image "registry.redhat.io/container-native-virtualization/virtio-win@sha256:326cbe461af4c34eba009b93a2a103181d90ca225f49be99d2fa152149b685ef"
  Warning  Failed          11s (x2 over 37s)  kubelet            Error: ImagePullBackOff
  Normal   Pulling         0s (x3 over 38s)   kubelet            Pulling image "registry.redhat.io/container-native-virtualization/virtio-win@sha256:326cbe461af4c34eba009b93a2a103181d90ca225f49be99d2fa152149b685ef"



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

How reproducible:


Steps to Reproduce:
1. Create Windows-10 VM from catalog 
2. Select boot from CD (provide iso)
3. Add blank disk to provide root disk
4. Select mount windows drivers disk

Actual results:
VM gets created but goes into ImagePullBackOff status

Expected results:
VM should be able to pull image from the registry

Additional info:

As a workaround mentioned below,

Link: https://catalog.redhat.com/software/containers/container-native-virtualization/virtio-win/5c8a9ce65a13464733ed0946?architecture=amd64&container-tabs=gti

Run below command on bastion.

oc import-image container-native-virtualization/virtio-win:v4.12.1-3 --from=registry.redhat.io/container-native-virtualization/virtio-win:v4.12.1-3 --confirm


- Stop the VM
- Edit the windows-drivers-disk 
- In containers remove everything after virtio-win.

Before:
registry.redhat.io/container-native-virtualization/virtio-win@sha256:326cbe461af4c34eba009b93a2a103181d90ca225f49be99d2fa152149b685ef

After:
registry.redhat.io/container-native-virtualization/virtio-win

- Start the VM.