Description of problem: Running deprovision for playbooks/kubevirt.yml does not remove all the resources. 1) /etc/cni/net.d/00-multus.conf existed even after deprovision. 2) kubevirt CRD still existed and did not get removed. Version-Release number of selected component (if applicable): cnv-1.4 How reproducible: Steps to Reproduce: 1. on the master ; cd /usr/share/ansible/kubevirt-ansible 2. ansible-playbook --connection local playbooks/kubevirt.yml -e @vars/cnv.yml -e registry_url=registry_url:8888 -e apb_action=deprovision 3. Actual results: 1) /etc/cni/net.d/00-multus.conf existed even after deprovision. 2) kubevirt CRD still existed and did not get removed. Expected results: Should deprovision cleanly all the resources.
@Dan, is this handled in the operator? should we assign this to you?
> 1) /etc/cni/net.d/00-multus.conf existed even after deprovision. This is a known behavior of the CNI DaemonSets. We have CNV-175 daemonsets should clean after themselves during shutdown to track this, but it is unlike to happen soon. > 2) kubevirt CRD still existed and did not get removed Which CRD are you referring to? In any case, these issue are not going to be addressed in kubevirt-ansible. I suggest this bug is closed and converted into acceptance criteria for KNIP-208 Deploy all of CNV components via operators