kubernetes: e2e conformance tests doesn`t cleanup psp and clusterRole 'e2e-test-privileged-psp'
What happened:
I executed all e2e tests named [Conformance], they ran successfully. After the tests were ran, a psp e2e-test-privileged-psp and a clusterRole e2e-test-privileged-psp were left in the cluster.
What you expected to happen: the conformance tests will clean up properly
How to reproduce it (as minimally and precisely as possible):
run all tests named with [Conformance] and check the cluster afterwards with:
kubectl get psp e2e-test-privileged-psp kubectl get clusterrole e2e-test-privileged-psp
Anything else we need to know?:
Environment:
- Kubernetes version (use
kubectl version): v1.18.4 - Cloud provider or hardware configuration: VIO
- OS (e.g:
cat /etc/os-release): Ubuntu 19.10 - Kernel (e.g.
uname -a): 5.3.0-46-generic - Install tools:
- Network plugin and version (if this is a network-related bug):
- Others:
[Conformance] matched 261 tests from the suite in my case:
[2020-06-29T09:54:33.882Z] Ran 261 of 4992 Specs in 792.462 seconds
[2020-06-29T09:54:33.882Z] SUCCESS! -- 261 Passed | 0 Failed | 0 Pending | 4731 Skipped
About this issue
- Original URL
- State: open
- Created 4 years ago
- Comments: 23 (14 by maintainers)
I think this ought to be fixed anyhow, as conformance tests are widely run, but I don’t know that anyone is really staffed to focus on this, so I froze it to make sure it at least stays tracked. It’s for sure a real issue.
@BenTheElder Ah right, makes sense. As it’s otherwise pretty low priority it probably doesn’t make sense to do anything until then. (except somebody volunteers)
@codemanufaktur: This issue is currently awaiting triage.
If a SIG or subproject determines this is a relevant issue, they will accept it by applying the
triage/acceptedlabel and provide further guidance.The
triage/acceptedlabel can be added by org members by writing/triage acceptedin a comment.Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.