Bug 1688807

Summary:	unable to de-provision cleanly using playbooks/kubevirt.yml
Product:	Container Native Virtualization (CNV)	Reporter:	Kedar Bidarkar <kbidarka>
Component:	Installation	Assignee:	Ohad Levy <ohadlevy>
Status:	CLOSED WONTFIX	QA Contact:	Irina Gulina <igulina>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.0	CC:	cnv-qe-bugs, danken, ipinto, ncredi, rhallise
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-20 11:08:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 1 Kedar Bidarkar 2019-03-14 13:53:47 UTC

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.

Comment 2 Nelly Credi 2019-03-19 13:39:24 UTC

@Dan, is this handled in the operator?
should we assign this to you?

Comment 3 Dan Kenigsberg 2019-03-20 11:08:13 UTC

> 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