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:
[Machines] vCPU and CPU topology settings could not be saved

Version-Release number of selected components (if applicable):
cockpit-machines-291-1.el9.noarch
cockpit-292-1.el9.x86_64
libvirt-dbus-1.4.1-5.el9.x86_64
libvirt-client-9.3.0-2.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Prepare a running VM like cirros, enter vm details page

2. Click edit after CPU in Overview tab, click apply without any changes.

There is error on the dialog:
vCPU and CPU topology settings could not be saved
ERROR unsupported configuration: CPU topology doesn't match maximum vcpu count

3. Click Cancel, then click edit again, change Mode to a different value like host-model , click Apply
The same error occurs, but the changes to the Mode is successful, there will be changes pending icon and the changes took effect after shut down the vm.

4. Click edit again, change vCPU count to 1, click Apply.
Same error occurs, and the changes did not take effect.


Actual results:
As above.

Expected results:
No error occurs.

Additional info:

https://github.com/cockpit-project/cockpit-machines/pull/1122

Verified with packages:
cockpit-machines-293-1.el9.noarch
cockpit-295-1.el9.x86_64
libvirt-dbus-1.4.1-5.el9.x86_64
libvirt-client-9.3.0-2.el9.x86_64

Steps:
1. Prepare a running VM like cirros, enter vm details page

2. Click edit after CPU in Overview tab, click apply without any changes.
Dialog closed without error message.

3. Click edit again, change Mode to a different value like host-model , click Apply
No error occurs, there will be changes pending icon and the changes took effect after shut down the vm.

4. Click edit again, change vCPU count to 1, click Apply.
No error occurs, there will be changes pending icon and the changes took effect after shut down the vm.

So 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-machines 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-2023:6336