Bug 1753997 - volumeMode is not passed when cloning a DataVolume
Summary: volumeMode is not passed when cloning a DataVolume
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.2.0
Assignee: Filip Krepinsky
QA Contact: Radim Hrazdil
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-20 13:39 UTC by Radim Hrazdil
Modified: 2019-10-16 06:41 UTC (History)
4 users (show)

Fixed In Version: 4.2.0-0.nightly-2019-09-20-225712
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:41:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 2794 0 'None' 'closed' 'kubevirt: take volume mode into account when cloning VMs' 2019-11-18 06:46:42 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:41:54 UTC

Description Radim Hrazdil 2019-09-20 13:39:45 UTC 
Description of problem:
When cloning a VM, the cloned DataVolume doesn't get the volumeMode value from the original (source) DataVolume

Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-09-17-232025

How reproducible:
100%

Steps to Reproduce:
1. Create a VM from URL source using wizard
2. Clone the VM
3.

Actual results:
Error in VM Events:
Error creating DataVolume asdasdasdasd-clone-asdasdasdasd-rootdisk-clone: admission webhook "datavolume-validate.cdi.kubevirt.io" denied the request: Source and target volume modes do not match

Expected results:


Additional info:
Comment 2 errata-xmlrpc 2019-10-16 06:41:39 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/RHBA-2019:2922
Note You need to log in before you can comment on or make changes to this bug.