Bug 1685911

Summary:	Allow uninstallation of KubeVirt by deleting the namespace
Product:	Container Native Virtualization (CNV)	Reporter:	Yan Du <yadu>
Component:	Virtualization	Assignee:	Fabian Deutsch <fdeutsch>
Status:	CLOSED DUPLICATE	QA Contact:	Israel Pinto <ipinto>
Severity:	low	Docs Contact:
Priority:	low
Version:	1.4	CC:	cnv-qe-bugs, dvossel, eudyonasi123, fdeutsch, igulina, ncredi, sgott
Target Milestone:	---	Keywords:	RFE
Target Release:	2.1.0
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-07-23 12:13:15 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:

Description Yan Du 2019-03-06 09:44:58 UTC

Description of problem:

$ oc get project kubevirt
NAME       DISPLAY NAME   STATUS
kubevirt                  Terminating

Version-Release number of selected component (if applicable):
openshift v3.11.69
kubernetes v1.11.0+d4cacc0
CNV 1.4

How reproducible:
not sure

Steps to Reproduce:
1. Setup up a cluster openshift+cnv
2. Make sure all the kubevirt components are deployed in the cluster
3. Delete the kubevirt project
# oc delete project kubevirt
4. Check the project
5. Check the log on master controller

Actual results:
4. kubevirt project keeps in Terminating status for a long time
5. Got some log from the master:

E0227 02:25:11.137161       1 namespace_controller.go:148] unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server could not find the requested resource, subresources.kubevirt.io/v1alpha3: the server is currently unable to handle the request, upload.cdi.kubevirt.io/v1alpha1: the server could not find the requested resource
E0227 02:25:11.788511       1 namespace_controller.go:148] unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server could not find the requested resource, subresources.kubevirt.io/v1alpha3: the server is currently unable to handle the request, upload.cdi.kubevirt.io/v1alpha1: the server could not find the requested resource
E0227 02:25:13.094867       1 namespace_controller.go:148] unable to retrieve the complete list of server APIs: subresources.kubevirt.io/v1alpha3: the server is currently unable to handle the request, upload.cdi.kubevirt.io/v1alpha1: the server could not find the requested resource
E0227 02:25:15.676392       1 namespace_controller.go:148] unable to retrieve the complete list of server APIs: subresources.kubevirt.io/v1alpha3: the server is currently unable to handle the request
E0227 02:25:20.812375       1 namespace_controller.go:148] unable to retrieve the complete list of server APIs: subresources.kubevirt.io/v1alpha3: the server is currently unable to handle the request


Expected results:
Kubevirt project can be deleted normally

Additional info:

I met same problem once when we were still using subresources.kubevirt.io/v1alpha2, the kubevirt project can not deleted and keep in Terminating, but after I delete the apiserivers (#oc delete apiservices v1alpha2.subresources.kubevirt.io). the kubevirt can be deleted normally.
But for the subresources.kubevirt.io/v1alpha3, the workaround doesn't work anymore.

Comment 1 Yan Du 2019-03-06 09:57:36 UTC

And a question about the apiversion, seems there are two api versions, is it by designed?
$ oc get apiservices v1alpha1.kubevirt.io 
NAME                   CREATED AT
v1alpha1.kubevirt.io   2019-03-06T03:06:17Z
$ oc get apiservices v1alpha3.kubevirt.io 
NAME                   CREATED AT
v1alpha3.kubevirt.io   2019-03-06T03:05:14Z

Comment 3 Fabian Deutsch 2019-03-07 08:57:36 UTC

David, any idea?

Comment 4 David Vossel 2019-03-08 22:27:37 UTC

Something is wrong with this environment if there are two versions of the kubevirt.io apiservice. For me, that indicates something hasn't been cleaned up properly from a previous kubevirt install.


I'm really not sure what's going on here. Why are we trying to delete the kubevirt namespace?  That's not really the proper way to deprovision KubeVirt.

Comment 5 Yan Du 2019-03-11 02:15:59 UTC

(In reply to David Vossel from comment #4)
> Something is wrong with this environment if there are two versions of the
> kubevirt.io apiservice. For me, that indicates something hasn't been cleaned
> up properly from a previous kubevirt install.
>
I have checked the upstream env (deploy by kubevirt-ansible on a fresh OCP env), there are still two apiversion there.
 
> 
> I'm really not sure what's going on here. Why are we trying to delete the
> kubevirt namespace?  That's not really the proper way to deprovision
> KubeVirt.
Yes, the best way to deprovison kubevirt is using the kubevirt-ansbile playbook. Maybe deleting the project is a abnormal operation, but what if the user does that? Seems there is no appropriate way to recover the env except re-installing a new one.

Comment 6 Fabian Deutsch 2019-06-20 12:07:27 UTC

*** Bug 1712429 has been marked as a duplicate of this bug. ***

Comment 7 sgott 2019-07-23 12:13:15 UTC


*** This bug has been marked as a duplicate of bug 1712429 ***

Comment 8 Ehud Yonasi 2022-10-02 09:12:55 UTC

You can delete them directly:
kubectl / oc delete apiservices.apiregistration.k8s.io v1.subresources.kubevirt.io v1alpha3.subresources.kubevirt.io