Bug 1692592
Summary: | "Enable menu to select boot device shows 10 device listed with cdrom at 10th slot but when selecting 10 option the VM took 1 as option and boot with disk | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Pawan kumar Vilayatkar <pvilayat> | ||||
Component: | ovirt-engine | Assignee: | Nobody <nobody> | ||||
Status: | CLOSED ERRATA | QA Contact: | Beni Pelled <bpelled> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 4.2.8 | CC: | ahadas, bpelled, dconsoli, mkalinin, mtessun, rdlugyhe | ||||
Target Milestone: | ovirt-4.4.1 | Keywords: | TestOnly | ||||
Target Release: | --- | Flags: | rbarry:
needinfo-
lsvaty: testing_plan_complete- |
||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: |
Previously, items with number ten and higher on the BIOS boot menu were not assigned sequential indexes. This made it difficult to select those items. The current release fixes this issue. Now, items ten and higher are assigned letter indexes. Users can select those items by entering the corresponding letter.
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2020-08-04 13:16:58 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | 1693031 | ||||||
Bug Blocks: | |||||||
Attachments: |
|
Description
Pawan kumar Vilayatkar
2019-03-26 01:10:00 UTC
I tested on https://lab-rhevm.gsslab.brq.redhat.com (4.2.4.5). I can select #10 with "0", #11 with "-" and #12 with "=". No idea how to select anything past that. Also, this is not intuitive at all. This will need a platform bug, since it's in seabios. In the meantime, using the top row of keys is an acceptable workaround Deferring while we wait for platform Also note that, especially in run once mode, wetting the cdrom as the primary boot device works in testing. No need for the menu (In reply to Ryan Barry from comment #7) > Also note that, especially in run once mode, wetting the cdrom as the > primary boot device works in testing. No need for the menu Hi Pawan, did you see this suggestion? If you go run once and put CDRom as a first bootable device, it should be elected automatically without prompting. Can you please confirm this with the customer as a workaround and create a KCS for it? sync2jira sync2jira WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops Verified on: - RHV 4.4.0-0.26.master.el8ev Verification steps: 1. Create a VM with 10 disks. 2. Attach an ISO file by "Boot Options > Attach CD" 3. Check the "Boot Options > Enable menu to select boot device" 4. Start the VM and open console 5. Press ESC for the boot menu 6. Select the CD device by selecting some letter (a/b/c - screenshot attached) Result: - The VM is booted from the CD-ROM or any other device with a higher number than 9 by selecting a letter (screenshot attached) Created attachment 1672308 [details]
Boot menu with more than 9 devices
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: RHV Manager (ovirt-engine) 4.4 security, bug fix, and enhancement 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-2020:3247 |