Bug 1881453

Summary:	cleanup unused namespace for manila csi driver operator after upgrading from 4.5 to 4.6
Product:	OpenShift Container Platform	Reporter:	Qin Ping <piqin>
Component:	Documentation	Assignee:	Jesse Dohmann <jdohmann>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Wei Duan <wduan>
Severity:	low	Docs Contact:	Latha S <lmurthy>
Priority:	low
Version:	4.6	CC:	aos-bugs, jokerman, jsafrane, lmurthy, wduan, wsun, xtian
Target Milestone:	---	Flags:	xtian: needinfo- wduan: needinfo- wduan: needinfo-
Target Release:	4.6.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-12-07 20:19:04 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 Qin Ping 2020-09-22 12:18:39 UTC

Description of Problem:
cleanup unused namespace for manila csi driver operator after upgrading from 4.5 to 4.6

Version-Release number of selected component (if applicable):


How Reproducible:
Always


Steps to Reproduce:
1. install an OCP4.5 cluster on Openstack with manila service enabled
2. install manila csi driver operator by OLM
3. upgrade from 4.5 to 4.6.0 nightly build

Actual Results:
Upgrade successfully, but the openshift-manila-csi-driver-operator ns is still there but not be used anymore

Expected Results:
openshift-manila-csi-driver-operator namespace is unused in 4.6, operator pod is in openshift-cluster-csi-drivers ns. Clean up this unused namespace.

Comment 1 Jan Safranek 2020-09-22 14:13:17 UTC

Manila operator namespace is chosen by users, openshift-manila-csi-driver-operator is just the default one. Users may use the namespace also for other things, therefore we do not remove the namespace automatically. We could perhaps document that after migration to CVO, the original Manila operator namespace may be empty and cluster admins may need to delete it manually. Perhaps somewhere around this: https://github.com/openshift/openshift-docs/pull/25458/files#diff-799468e7defe63964fd0a036625e2353R220

Comment 3 Jesse Dohmann 2021-10-04 20:37:13 UTC

Preview link: https://deploy-preview-37066--osdocs.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-6-release-notes?utm_source=github&utm_campaign=bot_dp#ocp-4-6-csi-driver-cso

Link to PR: https://github.com/openshift/openshift-docs/pull/37066

Comment 4 Wei Duan 2021-11-03 06:01:37 UTC

In the PR, I was suggesting to update the added words from:
The original `openshift-manila-csi-driver-operator` namespace might still exist and must be deleted manually by a cluster administrator.
to:
The original `openshift-manila-csi-driver-operator` namespace might still exist and need be deleted manually by a cluster administrator.

Comment 6 Jesse Dohmann 2021-11-09 17:35:05 UTC

@wduan I have updated the wording from "must" to "can", which is what I think needs to be communicated here

Comment 7 Wei Duan 2021-11-10 01:14:15 UTC

@Jesse, thanks for the update, this is what I expected.

Comment 8 Jesse Dohmann 2021-11-10 16:00:35 UTC

Great, i'll mark this as verified

Comment 9 Jesse Dohmann 2021-11-17 17:13:40 UTC

PR has been merged, thanks all!

Comment 10 Jesse Dohmann 2021-12-07 20:19:04 UTC

updated docs: https://docs.openshift.com/container-platform/4.6/release_notes/ocp-4-6-release-notes.html#ocp-4-6-csi-driver-cso

closing ticket