Bug 2182056 - Cloned VM should not use the same PVC of the source VM
Summary: Cloned VM should not use the same PVC of the source VM
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 4.13.0
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ---
: 4.14.0
Assignee: Aviv Turgeman
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks: 2182538 2182755
TreeView+ depends on / blocked
 
Reported: 2023-03-27 12:32 UTC by Guohua Ouyang
Modified: 2023-09-25 16:51 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2182538 2182755 (view as bug list)
Environment:
Last Closed: 2023-08-01 14:51:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
clone VM PVC (158.40 KB, image/png)
2023-03-27 12:32 UTC, Guohua Ouyang
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt-ui kubevirt-plugin pull 1201 0 None open [WIP] Bug 2182056: Cloned VM should not use the same PVC of the source VM 2023-03-28 11:18:52 UTC
Red Hat Issue Tracker CNV-27464 0 None None None 2023-03-27 12:34:04 UTC
Red Hat Product Errata RHSA-2023:4421 0 None None None 2023-08-01 14:52:14 UTC

Description Guohua Ouyang 2023-03-27 12:32:08 UTC
Created attachment 1953933 [details]
clone VM PVC

Description of problem:
Create a VM and wait for it becomes running, clone the VM, check the VM disk, it use the same PVC of the source VM, which is wrong as when this VM is up, the source VM is not able to turn up. And also it causes confused delete issues, from what I see the VM is stucking at terminating status forever when delete both of them at the same time.

It's happens on 4.12 and 4.13, regression from 4.11.

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


How reproducible:


Steps to Reproduce:
1. Create a VM and wait for it's up
2. Clone a VM from it
3. Verify the VM disk, same as the source VM 
4. When the cloned VM is up, try to start the source VM, source VM is not able to up.

Actual results:
Cloned VM PVC is same with source VM's PVC

Expected results:
Cloned VM use its own PVC.

Additional info:

Comment 3 Guohua Ouyang 2023-03-31 05:30:39 UTC
verified with v4.14.0-755

Comment 12 errata-xmlrpc 2023-08-01 14:51:33 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 (Important: OpenShift Virtualization 4.12.5 security and bug fix 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.

https://access.redhat.com/errata/RHSA-2023:4421


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