Bug 2101335

Summary: Clone action enabled in VM list kebab button for a VM in CrashLoopBackOff state
Product: Container Native Virtualization (CNV) Reporter: Adolfo Aguirrezabal <aaguirre>
Component: User ExperienceAssignee: Tal Nisan <tnisan>
Status: CLOSED ERRATA QA Contact: Guohua Ouyang <gouyang>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.11.0CC: gouyang, ycui
Target Milestone: ---   
Target Release: 4.12.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-01-24 13:36:58 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:
Attachments:
Description Flags
Clone enabled while in CrashLoopBackOff none

Description Adolfo Aguirrezabal 2022-06-27 08:19:30 UTC 
Created attachment 1892908 [details]
Clone enabled while in CrashLoopBackOff

Created attachment 1892908 [details]
Clone enabled while in CrashLoopBackOff

Description of problem:
From the VM list view, when a VM is in CrashLoopBackOff state, the 'Clone' action is enabled in the kebab menu for that VM, and it can be cloned.

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


How reproducible: Can be reproduced consistently


Steps to Reproduce:
1. Have a VM in CrashLoopBackOff state.
2. Access the VM list view.
3. Check the kebab menu for the VM in CrashLoopBackOff state.

Actual results:
1. The 'Clone' action is enabled.
2. The VM in CrashLoopBackOff state can be cloned.

Expected results:
1. The 'Clone' action is disabled.
2. The VM in CrashLoopBackOff state cannot be cloned.

Additional info: Also reproduced with other error states like ErrImagePull or ImagePullBackOff.
Comment 1 Guohua Ouyang 2022-07-27 04:44:36 UTC 
verified in v4.12.0-88
Comment 6 errata-xmlrpc 2023-01-24 13:36:58 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.0 Images security 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:0408