Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
In 'Installation type' is ''Download an OS", "Local Install Media" and "URL", VM rows will be extended automatically. For "Network Boot (PXE)" and "Import VM", VM rows won't be extended
Version-Release number of selected components (if applicable):
cockpit-machines-223-1.el8.noarch
libvirt-dbus-1.3.0-2.module+el8.3.0+6423+e4cb6418.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Create a VM with 'Network Boot (PXE)'
2. Create a VM with 'Import VM'
Actual results:
1. After step 1, the VM row will not be extended
2. After step 2, the VM row will not be extended
Expected results:
1. After step 1, the VM row should be extended
2. After step 2, the VM row should be extended
This BZ is not relevant any more, since version 231 where we redisigned the VMs page to not have expandable rows, rather the VMs details are now in a separate page.
When the user initiates now an installation they will not be automatically brought to the Vms details page, rather they will see the new VM in the Vms list, and once console is available they will be able to click the link to get redirected to the VM's details.
Pre-verified Versions:
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 through "Import VM"
2 Create a VM through "Network boot(PXE)"
Pre-verified Results:
1 After creation successful, no tab shown for the VM, and it will go to the detail page of the VM after clicking the name of the VM row
2 After creation successful, no tab shown for the VM, and it will go to the detail page of the VM after clicking the name of the VM row
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 through "Import VM"
2 Create a VM through "Network boot(PXE)"
Pre-verified Results:
1 After creation successful, no tab shown for the VM, and it will go to the detail page of the VM after clicking the name of the VM row
2 After creation successful, no tab shown for the VM, and it will go to the detail page of the VM after clicking the name of the VM row
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