After running KubeVirt functional tests with --deploy-testing-infra flag, we can observe some leftovers in the cluster:
cdi-http-import-server replicaset and pod
disks-images-provider pods
...
What you expected to happen:
All the resources which are created by DeployTestingInfrastructure() function in tests/utils.go cluster should be deleted by WipeTestingInfrastructure().
How to reproduce it (as minimally and precisely as possible):
Run KubeVirt functional tests with --deploy-testing-infra.
Anything else we need to know?:
Most of the leftovers are resources created by manifests/testing/disks-images-provider.yaml.in.
My guess is that Deployments and DaemonSets are deleted but not recursively leaving their Pods behind them.
Environment:
KubeVirt version (use virtctl version): v0.13.3
Kubernetes version (use kubectl version): v1.11.0+d4cacc0
Is this a BUG REPORT or FEATURE REQUEST?:
What happened:
After running KubeVirt functional tests with
--deploy-testing-infra
flag, we can observe some leftovers in the cluster:What you expected to happen:
All the resources which are created by DeployTestingInfrastructure() function in
tests/utils.go
cluster should be deleted by WipeTestingInfrastructure().How to reproduce it (as minimally and precisely as possible):
Run KubeVirt functional tests with
--deploy-testing-infra
.Anything else we need to know?:
Most of the leftovers are resources created by
manifests/testing/disks-images-provider.yaml.in
.My guess is that Deployments and DaemonSets are deleted but not recursively leaving their Pods behind them.
Environment:
virtctl version
): v0.13.3kubectl version
): v1.11.0+d4cacc0