Bug 1678412

Summary:	[Docs] Known issue when deleting a PVC when a CDI import is failing
Product:	Container Native Virtualization (CNV)	Reporter:	Adam Litke <alitke>
Component:	Documentation	Assignee:	Pan Ousley <pousley>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Irina Gulina <igulina>
Severity:	high	Docs Contact:
Priority:	high
Version:	1.4	CC:	alitke, cnv-qe-bugs, ncredi
Target Milestone:	---
Target Release:	1.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	1.4	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-28 16:39:06 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 Adam Litke 2019-02-18 17:41:42 UTC

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.

Comment 1 Pan Ousley 2019-02-18 22:26:46 UTC

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) :)

Comment 2 Adam Litke 2019-02-20 21:48:26 UTC

I agree we can leave out the reasoning.  Bug here: https://bugzilla.redhat.com/show_bug.cgi?id=1673683

Comment 3 Pan Ousley 2019-02-20 22:22:50 UTC

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

Comment 4 Irina Gulina 2019-02-21 09:31:00 UTC

Looks good. Thanks.

Comment 5 Pan Ousley 2019-02-28 16:39:06 UTC

The requested content was published here: https://docs.openshift.com/container-platform/3.11/cnv_release_notes/cnv_release_notes.html#RN_known_issues