Snapshot tests are leaving namespaces behind as discovered in - https://bugzilla.redhat.com/show_bug.cgi?id=1814282 This is a follow up https://bugzilla.redhat.com/show_bug.cgi?id=1814282 because we want to fix snapshot e2es via a different PR.
Hi Huffman, I performed two scenarios as below: 1. After creating volumesnapshot successfully --> Delete volumesnapshotclass --> Delete namespace, the namespace was deleted successfully 2. When this is a not READYTOUSE volumesnapshot exists --> Delete volumesnapshotclass --> Delete namespace, the namespace was is always in "Terminating" It should linkd to another issue like bug 1867167 or 1842747 (BTW, do you think they are the same root cause?) $ oc get project wduan-test NAME DISPLAY NAME STATUS wduan-test Terminating $ oc get volumesnapshot -n wduan-test NAME READYTOUSE SOURCEPVC SOURCESNAPSHOTCONTENT RESTORESIZE SNAPSHOTCLASS SNAPSHOTCONTENT CREATIONTIME AGE mysnapshot-01 false mypvc01 csi-aws-ebs-snapclass 25m Please let me know if this fix is only for scenario 1? Thanks.
Nightly used. 4.6.0-0.nightly-2020-08-10-200500
You're correct that this bug is only for the first scenario. The second scenario can have a couple of different causes, such as those tracked by the linked bugs. My understanding of the bugs is below: - BZ1867167 - When the underlying PV is not created by a CSI driver, we never remove the source finalizer from the snapshot, as it never finishes creation. There's a WIP PR to address this that checks the volume type and will remove the finalizer. - BZ1842747 - In this case the PV is from a correct driver, but not yet bound. This requires a different fix than BZ1867167, as there's been discussion upstream regarding how to handle this behavior.
Thanks for the explaination, it is more clear than reading all the comments for this bug and original bug. I will mark "Verified" as we discussed above.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196