Bug 2054382 - A VM created using the webUI, gets created with volumeMode as Filesystem instead of Block
Summary: A VM created using the webUI, gets created with volumeMode as Filesystem inst...
Keywords:
Status: CLOSED DUPLICATE of bug 2049762
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 4.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Tal Nisan
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-14 20:09 UTC by Kedar Bidarkar
Modified: 2022-02-15 00:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-15 00:07:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Kedar Bidarkar 2022-02-14 20:09:25 UTC 
Description of problem:
 VM created using the webUI uses volumeMode as Filesystem instead of Block

Version-Release number of selected component (if applicable):
1) Setup Build, v4.10.0-674	IIB Image: 175814
2) version   4.10.0-rc.2   True        False         4h50m   Cluster version is 4.10.0-rc.2

How reproducible:
Via WebUI using the Wizard and Selecting "customize virtual machine"

Steps to Reproduce:
1) Create a rhel8-5 VM via templates using the Wizard, from the WebUI
2) Choose ocs-rbd storage from the webUI, check the "Apply storage profile"
3) In the VM spec, we still see VolumeMode as "FileSystem", it should have been "Block" volumeMode
4) Even, If I go and manually choose "Block" volumeMode, I still see  "FileSystem" in the created VM Spec file.

Actual results:
VM gets created with "Filesystem" volumeMode

Expected results:
VM should have got created with "Block" volumeMode

Additional info:
Comment 1 Guohua Ouyang 2022-02-15 00:07:44 UTC 
This is caused by customized wizard cannot save storage changes, duplicating with bug 2049762.

*** This bug has been marked as a duplicate of bug 2049762 ***
Note You need to log in before you can comment on or make changes to this bug.