RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1880175 - [Machines] Unable to select cdrom / ISO boot device after installation
Summary: [Machines] Unable to select cdrom / ISO boot device after installation
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: cockpit-appstream
Version: 8.2
Hardware: x86_64
OS: FreeBSD
unspecified
medium
Target Milestone: rc
: 8.4
Assignee: Simon Kobyda
QA Contact: YunmingYang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-17 20:37 UTC by Mr.D
Modified: 2021-05-18 15:53 UTC (History)
3 users (show)

Fixed In Version: 233.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-18 15:53:11 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Fig2 (40.18 KB, image/png)
2020-09-17 20:38 UTC, Mr.D 		no flags Details
Fig1 (62.51 KB, image/png)
2020-09-17 20:38 UTC, Mr.D 		no flags Details
Fig3 (49.85 KB, image/png)
2020-09-17 20:38 UTC, Mr.D 		no flags Details
View All

Description Mr.D 2020-09-17 20:37:04 UTC 
Description of problem:

Unable to select an option to boot device to CD-ROM / ISO. 

+ Workaround does not help:
The wait time for pressing F8 to select boot device is too short as the console takes longer to connect, thus impossible to use this method.


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

cockpit.x86_64                                211.3-1.el8                                    @anaconda                        
cockpit-bridge.x86_64                         211.3-1.el8                                    @anaconda                        
cockpit-machines.noarch                       211.3-1.el8                                    @rhel-8-for-x86_64-appstream-rpms
cockpit-packagekit.noarch                     211.3-1.el8                                    @AppStream                       
cockpit-system.noarch                         211.3-1.el8                                    @anaconda                        
cockpit-ws.x86_64                             211.3-1.el8                                    @anaconda                        
subscription-manager-cockpit.noarch           1.26.20-1.el8_2                                @rhel-8-for-x86_64-baseos-rpms  


How reproducible:

1. Install a guest VM as normal.
2. The trying to boot to CD-ROM to reinstall.


Steps to Reproduce:

1. Install VM with Redhat guest as normal.
2. After Normal boot power off the guest.
3. The CD-Rom is removed from boot order or moved to lower priority
4. Note: ( F8 to select boot device is impossible. The Console takes too long to load, thus the F8 wait time has passed )
5. Select the VM "overview" tab (Fig2.png)
6. Select the "Boot Order" link 
7. In the list of boot choices, CD-ROM is not presented.


Actual results:

See Attached Fig1.png -- CD-Rom is not listed
See Attached Fig3.png -- CD-Rom is attached

Expected results:

The CD-ROM would be listed as a selectable boot option.
Comment 1 Mr.D 2020-09-17 20:38:01 UTC 
Created attachment 1715275 [details]
Fig2

Fig2
Comment 2 Mr.D 2020-09-17 20:38:33 UTC 
Created attachment 1715276 [details]
Fig1

Fig1
Comment 3 Mr.D 2020-09-17 20:38:55 UTC 
Created attachment 1715277 [details]
Fig3

fig3
Comment 4 Mr.D 2020-09-17 20:49:21 UTC 
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.
Comment 5 Martin Pitt 2020-09-25 09:52:35 UTC 
Moving to correct component. Simon, can you please have a look? Thanks!
Comment 6 Simon Kobyda 2020-09-29 11:22:08 UTC 
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
Comment 7 Martin Pitt 2020-09-29 11:25:11 UTC 
Thanks Simon! Yunming, can you please qe-ack?
Comment 9 Katerina Koukiou 2020-11-06 12:15:40 UTC 
https://github.com/cockpit-project/cockpit/pull/14679 was merged. This will be available with cockpit-232.
Comment 10 YunmingYang 2020-12-04 12:54:03 UTC 
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’.
Comment 13 YunmingYang 2020-12-13 18:07:29 UTC 
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’.
Comment 15 errata-xmlrpc 2021-05-18 15:53:11 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 (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
Note You need to log in before you can comment on or make changes to this bug.