Description of problem: Using kubevirt-apb to deploy kubevirt, I get vm-template-fedora deployed with that: [root@cnv-executor-lbednar-master1 ~]# oc get template --all-namespaces | grep fedora openshift vm-template-fedora OCP KubeVirt Fedora 27 VM template 3 (1 blank) 1 And it points to unavailable image: [root@cnv-executor-lbednar-master1 ~]# oc get template -n openshift vm-template-fedora -o yaml | grep image: image: registry:5000/kubevirt/fedora-cloud-registry-disk-demo:devel This cause that vm creation being stuck on pulling this image: [root@cnv-executor-lbednar-master1 ~]# oc get pod virt-launcher-myvm-g4p8p -o yaml ... TRIMMED ... - image: registry:5000/kubevirt/fedora-cloud-registry-disk-demo:devel imageID: "" lastState: {} name: volumeregistryvolume ready: false restartCount: 0 state: waiting: message: Back-off pulling image "registry:5000/kubevirt/fedora-cloud-registry-disk-demo:devel" reason: ImagePullBackOff Version-Release number of selected component (if applicable): brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/cnv12-tech-preview/kubevirt-apb 1.2-4 f9ffe7e42b6b 3 days ago 524 MB How reproducible: 100% Steps to Reproduce: 1. Deploy kubevirt using APB 2. Create VM from template neither using "oc process" or via webconsole - pass NAME & CPU_CORES & MEMORY params 3. Observe status of virt-launcher pod Actual results: Unable to pull image: Back-off pulling image "registry:5000/kubevirt/fedora-cloud-registry-disk-demo:devel" Expected results: Running VM or remove these template from APB ? Additional info:
The registry comes from the upstream template https://github.com/kubevirt/kubevirt/blob/master/cluster/examples/vm-template-fedora.yaml#L53. If the registry is wrong can you file an issue upstream against kubevirt/kubevirt? I'm not sure what the expectation is downstream of this image because it would need to be built in OSBS to be distributed.
@Ryan that registry works for u/s because they build and push this image into local registry. But it doesn't work for d/s because this image wasn't built neither pushed into local registry. If we want to ship this template, we will have to somehow address that.
For 1.2 I would not mind that much and keep it as is.
will leave as is for 1.2 and we can address in the future.
Isnt kubevirt apb going to be replaced with the operator in 1.4? i see 2 options - resolve in 1.3 or close as wont fix
Needs a release note but I'm comfortable with WONTFIX.
@Pan I guess you should be aware of this
@Nelly, thanks for the heads up. I added a release note here: https://github.com/openshift/openshift-docs/pull/12518/commits/8931eb294478260128d4afa8b903030703edf7f6 Can you please check it for accuracy? We can take it out if we end up not using APBs.
doc looks fine