Bug 2207468 - An error occurred while cloning a VM
Summary: An error occurred while cloning a VM
Keywords:
Status: VERIFIED
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 4.14.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.14.0
Assignee: Ugo Palatucci
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-16 02:24 UTC by Guohua Ouyang
Modified: 2023-07-13 05:33 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
vm clone error (163.15 KB, image/png)
2023-05-16 02:24 UTC, Guohua Ouyang
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt-ui kubevirt-plugin pull 1327 0 None open Bug 2207468: Clone vm without CR 2023-06-07 12:20:22 UTC
Red Hat Issue Tracker CNV-28828 0 None None None 2023-05-16 02:25:36 UTC
Red Hat Issue Tracker CNV-29440 0 None None None 2023-06-07 08:08:34 UTC

Description Guohua Ouyang 2023-05-16 02:24:13 UTC
Created attachment 1964813 [details]
vm clone error

Description of problem:
Clone a VM and An error occurred:
"the server does not allow this method on the requested resource"

However, the VM is cloned even with this error occurred.

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


How reproducible:


Steps to Reproduce:
1. Clone a VM
2.
3.

Actual results:
An error occurred

Expected results:
No error occurred

Additional info:

Comment 1 Guohua Ouyang 2023-06-06 00:37:42 UTC
Mark this as a regression as it didn't happen before.
Once the bug is fixed, Will backport it to 4.13.1

Comment 2 Guohua Ouyang 2023-06-06 01:35:03 UTC
It only happens on VM created from templates, not on VM created from instanceTypes.

Comment 3 Guohua Ouyang 2023-07-12 08:48:19 UTC
verified on kubevirt-console-plugin-rhel9:v4.14.0-2110


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