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.

Description of problem:

Currently, it is not possible to set boot order through cockpit UI

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

cockpit-machines-184-1.el8.noarch

How reproducible:

100% 

Steps to Reproduce:
1. Cockpit > Virtual Machines > Select VM or Create VM
2. No option to set boot order 


Actual results:

There is no option to allow user to set boot order on a VM, while creating it or after

Expected results:

User should be able to set from which source the VM should boot

This is being worked on in https://github.com/cockpit-project/cockpit/pull/10863

Test Versions:
cockpit-machines-193-1.el8.noarch
libvirt-dbus-1.2.0-2.module+el8.1.0+2983+b2ae9c0a.x86_64

Test Steps:
1.Create an off VM and click the 'boot order' on the overview tab for each VM row
2.Set the network as the first boot option, the disk as the second boot option, then click the 'Save' button
3.Run VM


Test Results:
The VM can run with network boot firstly. Then, if there is no PXE server, it will boot from the disk which is the second boot option.


According to the results, user can set boot order for the VM. So 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, 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-2019:3325