Bug 1843579

Summary:	[aws-ebs-csi-driver-operator] No indication of un-installation
Product:	OpenShift Container Platform	Reporter:	Jan Safranek <jsafrane>
Component:	Storage	Assignee:	Fabio Bertinatto <fbertina>
Status:	CLOSED WONTFIX	QA Contact:	Chao Yang <chaoyang>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.5	CC:	aos-bugs, chaoyang, fbertina
Target Milestone:	---
Target Release:	4.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-10 12:16:46 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 Jan Safranek 2020-06-03 15:14:08 UTC

When user removes AWSEBSDriver CR, the operator waits for all PVs provided by the driver to disappear and then it un-installs the CSI driver.

But there is no indication that it is happening, especially when a PV still exists.

How reproducible:
always

Steps to Reproduce:
1. Install the CSI driver (i.e., install the operator + create CR)
2. Create PVC + Pod that uses gp2-csi storage class, provided by the driver
3. Delete the AWSEBSDriver CR

Actual results:
OCP console shows everything as running (Available=true, Progressing=false), and there is no indication why the driver is not uninstalled.

Expected results:

Some indication that the operator waits for all PVs to be deleted. Question is, what is the right indication. A new condition Terminating = true, with "Waiting for 1 PV that use the driver to be removed"? Or re-use Progressing? But the operator is not progressing, it's stuck at existing PVs.

Comment 3 Jan Safranek 2020-07-10 12:16:46 UTC

In 4.6 we do not plan to support un-installation of CSI drivers. AWS EBS CSI driver + its operator is part of the cluster (when running on AWS).
We may fix it in 4.5.z, when more serious issue comes around.