Bug 1876743

Summary:	Should describe clear what to fill in Fstype if disk is block when create localvolume on web console
Product:	OpenShift Container Platform	Reporter:	Chao Yang <chaoyang>
Component:	Storage	Assignee:	Jan Safranek <jsafrane>
Storage sub component:	Local Storage Operator	QA Contact:	Chao Yang <chaoyang>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	low
Priority:	unspecified	CC:	aos-bugs, bniver, gmeno, jefbrown, jsafrane, madam, nthomas, ocs-bugs, rojoseph, sostapov
Version:	4.6
Target Milestone:	---
Target Release:	4.6.0
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:	2020-10-27 16:38:28 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 Chao Yang 2020-09-08 06:18:25 UTC

Description of problem:
Should describe clear what to fill in Fstype if disk is block when create localvolume on web console

Version-Release number of selected component (if applicable):
4.6.0-0.nightly-2020-09-03-191144
local-storage-operator.4.6.0-202009041839.p0

How reproducible:
Always

Steps to Reproduce:
1.Deploy LSO
2.Click localvolume
3.Check Storage Class Device
4.For FsType, default value is ext4
5.If choose VolumeMode as Block, FsType should fill with blank.
But there is no description how to fill FsType value here 

Actual results:
Fstype is not clear for customer how to create block storage class devices.

Expected results:
Add description about Fstype value when choose VolumeMode as Block.

Additional info:

Comment 1 Neha Gupta 2020-09-08 07:13:26 UTC

This is auto generated form based on the x-descriptors. This needs to handled via the backend. 
Also, the volume mode field dropdown should be moved above the FsType field dropdown, as its value gets change based on the volume mode selection.

Moving this to LSO team.

Comment 3 Rohan CJ 2020-09-08 07:57:22 UTC

The FSType field should be omitted when using volumeMode: Block

Comment 4 Michael Adam 2020-09-10 11:20:59 UTC

console RFE.

Should probably move to OCP, as it is an LSO piece.
But moving to OCS->management console first, for further triaging.

Comment 5 Neha Gupta 2020-09-14 06:34:53 UTC

This needs to fixed from the backend as the form are generated by the descriptors.

Comment 6 Jan Safranek 2020-09-15 12:17:44 UTC

We can't do cross-field validation, so I am updating the description to:

> File system type to create on empty volumes, such as "ext4" or "xfs". Used only when volumeMode is "Filesystem". Leave blank when volumeMode is "Block".

Comment 8 Chao Yang 2020-09-22 07:17:20 UTC

File system type to create on empty volumes, such as "ext4" or "xfs". Used only when volumeMode is "Filesystem". Leave blank when volumeMode is "Block". 
Above sentence is added 4.6.0-0.nightly-2020-09-21-030155
Update bz status.

Comment 11 errata-xmlrpc 2020-10-27 16:38:28 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 (OpenShift Container Platform 4.6 GA Images), 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/RHBA-2020:4196