Bug 2090043

Summary: "No resource selected" in vm boot order
Product: Container Native Virtualization (CNV) Reporter: Guohua Ouyang <gouyang>
Component: User ExperienceAssignee: Tal Nisan <tnisan>
Status: CLOSED ERRATA QA Contact: Guohua Ouyang <gouyang>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.11.0CC: cnv-qe-bugs, gouyang, ycui, yzamir
Target Milestone: ---   
Target Release: 4.11.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: 2022-09-14 19:34:47 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
boot order none

Description Guohua Ouyang 2022-05-25 02:13:33 UTC
Created attachment 1883007 [details]
boot order

Description of problem:
Create a VM via "Quick create VirtualMachine", in vm details page, it shows "No resource selected" in boot order.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Gilad Lekner 2022-05-31 07:55:45 UTC
@gouyang 
this is not a bug. the default disk will be selected which is the first disk if no disks with bootOrder are available.

@yzamir also says the boot order will move from details to the disks tab

Comment 2 Guohua Ouyang 2022-05-31 08:03:29 UTC
(In reply to Gilad Lekner from comment #1)
> @gouyang 
> this is not a bug. the default disk will be selected which is the first disk
> if no disks with bootOrder are available.
> 
Can we show the default bootOrder list instead of showing the text "No resource selected
VirtualMachine will attempt to boot from disks by order of appearance in YAML file"?


> @yzamir also says the boot order will move from details to the
> disks tab

Comment 3 Guohua Ouyang 2022-06-02 03:36:04 UTC
verified on v4.11.0-39

Comment 7 errata-xmlrpc 2022-09-14 19:34:47 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.11.0 Images 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-2022:6526