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: 
The VM can only be fold/unfold by clicking the arrow before the name of the vm

Version-Release number of selected component (if applicable):
cockpit-machines-222.1-1.el8.noarch
libvirt-dbus-1.3.0-2.module+el8.3.0+6423+e4cb6418.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Prepare a VM
2. Click the arrow before the name of the vm to fold/unfold it
3. Click the row of the name of the vm to fold/unfold it


Actual results:
In step 3, the vm can not to be fold/unfold like before.

Expected results:
In step 3, the vm should able to be fold/unfold like before.

Additional info:
Did we make this change intended ? But I think it's more convenient to fold/unfold the vm by clicking the row.
By the way, we can still fold/unfold by clicking the row on  storage pool page, so I think they should be consistent.

The tables should only expand when clicking on the toggle button, this is following the new design from Patternfly 4.
https://www.patternfly.org/v4/documentation/react/components/table#collapsible

I ported the Storage Pools and Networks tables to the new design, so now these two are consistent in matters of behavior with the VM one.

https://github.com/cockpit-project/cockpit/pull/14376

Relevant commits:
commit cf114780928e46c1e4b12ce1a5385fc65ba5f792
Author: Katerina Koukiou <kkoukiou>
Date:   Mon Jul 20 12:30:32 2020 +0200

    machines: Port Network List to ListingTable (PF4)
    
commit 263955e9db11396828d5a5d00fd7f83e6fe0c3ac
Author: Katerina Koukiou <kkoukiou>
Date:   Mon Jul 20 12:30:32 2020 +0200

    machines: Port StoragePool List to ListingTable (PF4)

Verified with package:
cockpit-machines-224-1.el8.noarch

Step:
1. Prepare a VM
2. Check Storage Pools and Networks tables and vms page, click the arrow before the name to fold/unfold them.


All consistent, so veyified.

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-2020:4705