If a CDI import into a PVC is failing (ie. due to an invalid URL) a request to delete the PVC may not delete the PVC immediately. Instead, the PVC may enter a Terminating phase because the importer Pod is stuck in a CrashLoopBackoff state. To resolve the issue, find the associated importer pod and delete it. The PVC will then finish deleting. The above situation requires documentation in the 1.4 known issues.
Made a few small changes, please review for accuracy: "If a CDI import into a PVC fails, a request to delete the PVC might not work immediately. Instead, the importer Pod gets stuck in a CrashLoopBackOff state, causing the PVC to enter a `Terminating` phase. To resolve this issue, find the importer pod associated with the PVC and delete it. The PVC will then be deleted." How important is it to mention the possible reasons for the CDI import failure ("ie. due to an invalid URL")? I took that out because we don't use parentheticals in the docs. If it's important I can add it in a sentence, but if this can happen for *any* reason, I think we should probably leave it out. Also, which BZ is the original so that I can add it to the text? (Sorry if you sent it earlier over Bluejeans) :)
I agree we can leave out the reasoning. Bug here: https://bugzilla.redhat.com/show_bug.cgi?id=1673683
Thanks Adam! Added the BZ. Moving to ON_QA. QE, here's the latest preview containing this release note: http://file.bos.redhat.com/pousley/022019/knownissues/cnv_release_notes/cnv_release_notes.html
Looks good. Thanks.
The requested content was published here: https://docs.openshift.com/container-platform/3.11/cnv_release_notes/cnv_release_notes.html#RN_known_issues