Created attachment 1535249 [details] failing provision Description of problem: I have uninstalled CNV with deprovision job, then tried installing it with provisioning, and it failed on "Wait until multus is running" Version-Release number of selected component (if applicable): kubevirt-ansible-0.12.3-1.f9f3ed4.src.rpm How reproducible: 3 attempts with new cluster -> deprovision -> provision and all failed Steps to Reproduce: 1. deprovision 2. provision Actual results: multus error Additional info: logs attached.
@Irina, can you please provide pod logs? is it just a timeout issue which got resolved eventually (we had a bug for it) or are the pods just failing to get into running state?
When you re-provision, do the new pods all fail to be scheduled? I've seen a similar failure occasionally in the past, where multus is the registered CNI plugin but it's been removed. So all pod creation after the removal of multus fails.
Created attachment 1535987 [details] pod logs
Adding Dan for visibility.
@pan something is probably wrong with the deprovision, we need to make it clear in the docs that deprovision and re-installing will fail
Hi Irina, I don't think this is a bug. from the pod log pulling image "registry.access.redhat.com/cnv-tech-preview/multus-cni:v1.4.0" this image don't exist. this is the latest image in the redhat registry https://access.redhat.com/containers/?architecture=AMD64#/registry.access.redhat.com/cnv-tech-preview/multus-cni/images/v1.3.0-2 logs from the pod error parsing HTTP 404 response body: invalid character 'F' looking for beginning of value: "File not found.\"" Error: ErrImagePull Back-off pulling image "registry.access.redhat.com/cnv-tech-preview/multus-cni:v1.4.0" maybe change the registry to a place where multus:v1.4 exist and try again?