Bug 1839982

Summary:	[CNV][DOC] Lack of explanation for StorageClass default accessMode in openshift-cnv kubevirt-storage-class-defaults
Product:	Container Native Virtualization (CNV)	Reporter:	Rafal Szmigiel <rszmigie>
Component:	Documentation	Assignee:	Bob Gaydos <bgaydos>
Status:	CLOSED ERRATA	QA Contact:	zhe peng <zpeng>
Severity:	low	Docs Contact:
Priority:	low
Version:	2.3.0	CC:	adellape, aspauldi, bgaydos, cnv-qe-bugs, ncredi, sbream, zpeng
Target Milestone:	---
Target Release:	2.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	2.4.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-28 19:10:07 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 Rafal Szmigiel 2020-05-26 07:29:33 UTC

Document URL: 
https://docs.openshift.com/container-platform/4.4/cnv/cnv_live_migration/cnv-live-migration.html

Section Number and Name: 

Describe the issue: 
In order to use LiveMigration the VM has to be deployed with RWX volume. Defaults in openshift-cnv kubevirt-storage-class-defaults are configured to provide RWO volumes so LiveMigration doesn't work by default. 

Suggestions for improvement: 
We should explain this setting in our CNV documentation and mention that in order to override this default setting for the specific StorageClass they should update the config map, for an instance:

$ export STORAGE_CLASS="nfs"
$ oc patch -n openshift-cnv cm kubevirt-storage-class-defaults -p '{"data":{"'${STORAGE_CLASS}'.accessMode":"ReadWriteMany"}}'

Additional information:

Comment 3 zhe peng 2020-06-15 02:41:55 UTC

Check with the doc,
already add change RWO to RWX for migration, move to verified.

Comment 9 zhe peng 2020-07-22 10:52:54 UTC

I review the test build, no other comments and can move this to verified.

Comment 14 errata-xmlrpc 2020-07-28 19:10:07 UTC

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, 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/RHSA-2020:3194