Bug 2182056
| Summary: | Cloned VM should not use the same PVC of the source VM | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Guohua Ouyang <gouyang> | ||||
| Component: | User Experience | Assignee: | Aviv Turgeman <aturgema> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Guohua Ouyang <gouyang> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.13.0 | CC: | gouyang, gveitmic, jsaucier, nashok, ycui | ||||
| Target Milestone: | --- | Keywords: | Regression | ||||
| Target Release: | 4.14.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 2182538 2182755 (view as bug list) | Environment: | |||||
| Last Closed: | 2023-08-01 14:51:33 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 2182538, 2182755 | ||||||
| Attachments: |
|
||||||
verified with v4.14.0-755 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 |
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: