Bug 1880175
| Summary: | [Machines] Unable to select cdrom / ISO boot device after installation | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Mr.D <mr.dk.vv> | ||||||||
| Component: | cockpit-appstream | Assignee: | Simon Kobyda <skobyda> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | YunmingYang <yunyang> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 8.2 | CC: | kkoukiou, mpitt, mr.dk.vv | ||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | 8.4 | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | FreeBSD | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | 233.1 | Doc Type: | If docs needed, set a value | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2021-05-18 15:53:11 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
Mr.D
2020-09-17 20:37:04 UTC
Created attachment 1715275 [details]
Fig2
Fig2
Created attachment 1715276 [details]
Fig1
Fig1
Created attachment 1715277 [details]
Fig3
fig3
Unclear if it related to "BZ # 1666825" as this ticket deals with attaching devices. This ticket is to address unable to select cd-rom boot order for existing attached medium. Moving to correct component. Simon, can you please have a look? Thanks! The problem is that cdrom properties are not shown in boot order dialog. So the cdrom is the empty disk you see in Figure 3. I posted a patch for that: https://github.com/cockpit-project/cockpit/pull/14679 Thanks Simon! Yunming, can you please qe-ack? https://github.com/cockpit-project/cockpit/pull/14679 was merged. This will be available with cockpit-232. Pre-verified Versions:
cockpit-224.2-1.el8.x86_64
cockpit-machines-233.1-1.el8.noarch
libvirt-dbus-1.3.0-2.module+el8.3.0+6423+e4cb6418.x86_64
Pre-verified Steps:
1 Create a VM with "Local install media", then follow the installation process, Click "Reboot" button on the installation GUI.
2 Open boot order dialog from VM detail page
3 Then shut off the VM, detach the cdrom
4 Re-attach cdrom
5 Open boot order dialog
6 Select the option that is the cdrom and also change it to the first boot option
7 Run the VM
Pre-verified Results:
1 After step 2, the option of cdrom in boot order dialog is shown as "disk Device cdrom Bus sata"
2 After step 5, the option of cdrom in boot order dialog is shown as "disk Pool default
Volume Fedora-Server-dvd-x86_64-31-1.9.iso"
3 After step 6, the boot order can be saved
4 After step 7, the VM will be booted from cdrom
According to the results, change ‘Verified’ status to ‘TESTED’.
Verified Versions:
cockpit-224.2-1.el8.x86_64
cockpit-machines-233.1-1.el8.noarch
libvirt-dbus-1.3.0-2.module+el8.3.0+6423+e4cb6418.x86_64
Verified Steps:
1 Create a VM with "Local install media", then follow the installation process, Click "Reboot" button on the installation GUI.
2 Open boot order dialog from VM detail page
3 Then shut off the VM, detach the cdrom
4 Re-attach cdrom
5 Open boot order dialog
6 Select the option that is the cdrom and also change it to the first boot option
7 Run the VM
Verified Results:
1 After step 2, the option of cdrom in boot order dialog is shown as "disk Device cdrom Bus sata"
2 After step 5, the option of cdrom in boot order dialog is shown as "disk Pool default
Volume Fedora-Server-dvd-x86_64-31-1.9.iso"
3 After step 6, the boot order can be saved
4 After step 7, the VM will be booted from cdrom
According to the results, move the status to ‘VERIFIED’.
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 (cockpit-appstream 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/RHBA-2021:1875 |