Bug 1911382 - "source volumeMode (Block) and target volumeMode (Filesystem) do not match" shows in VM Error
Summary: "source volumeMode (Block) and target volumeMode (Filesystem) do not match" s...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.7.0
Assignee: Matan Schatzman
QA Contact: Guohua Ouyang
Depends On:
TreeView+ depends on / blocked
Reported: 2020-12-29 02:47 UTC by Guohua Ouyang
Modified: 2021-02-24 15:49 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-02-24 15:49:10 UTC
Target Upstream Version:

Attachments (Terms of Use)
"source volumeMode (Block) and target volumeMode (Filesystem) do not match" (141.28 KB, image/png)
2020-12-29 02:47 UTC, Guohua Ouyang
no flags Details

System ID Private Priority Status Summary Last Updated
Github openshift console pull 7749 0 None closed Bug 1911382: If source PVC is selected, volumeMode changes to source volumeMode. 2021-01-25 10:31:50 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:49:26 UTC

Description Guohua Ouyang 2020-12-29 02:47:31 UTC
Created attachment 1742845 [details]
"source volumeMode (Block) and target volumeMode (Filesystem) do not match"

Description of problem:
"source volumeMode (Block) and target volumeMode (Filesystem) do not match" shows in VM Error when creating a vm in customize mode by selecting a source available template.

The customize wizard should detect and use the source dv's SC/AccessMode/VolumeMode.

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

How reproducible:

Steps to Reproduce:
1. upload image to rhel8 template via 
$ virtctl image-upload dv rhel8 --size=10Gi --image-path=./cirros.img --storage-class=ocs-storagecluster-ceph-rbd --volume-mode=Block --access-mode=ReadWriteMany --insecure -n openshift-virtualization-os-images
2. select rhel8 template in wizard
3. click "Customize" 
4. create the vm with defaults in customize mode

Actual results:
VM error with "source volumeMode (Block) and target volumeMode (Filesystem) do not match"

Expected results:
VM is created successfully.

Additional info:

Comment 1 Yaacov Zamir 2020-12-30 07:47:23 UTC
When fixing this bug look at this other bugs related to storage not using data available in the template to create storage in VM:

https://bugzilla.redhat.com/show_bug.cgi?id=1911382 - source volumeMode (Block) and target volumeMode (Filesystem) do not match" shows in VM Error
https://bugzilla.redhat.com/show_bug.cgi?id=1895169 - VM Template does not properly manage Mount Windows guest tools check box during VM creation (assigned Philip)
https://bugzilla.redhat.com/show_bug.cgi?id=1911418 -  The target storage class name is not displayed if default storage class is used (assigned Gilad)

Comment 3 Yaacov Zamir 2020-12-30 13:55:50 UTC
This issue is related to the "Golden Image" feature that is a customer request.
Using the golden image flow correctly may result in a VM creation fail.

Setting to blocker +

Comment 4 Matan Schatzman 2021-01-04 13:48:30 UTC
We had a discussion today about this bug with @rawagner , @yzamir , @mcarleto :

We have decided that the solution is:

1. using the volumeMode provided by source PVC.
2. disabling the dropdown option for the user to edit the volumeMode.
3. showing a small info message that the volumeMode is taken from the source PVC.

Comment 10 errata-xmlrpc 2021-02-24 15:49:10 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.