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.
[Machines] Change "Current allocation" won't take effect immediately for running vm
Version-Release number of selected components (if applicable):
cockpit-machines-294-1.el9.noarch
cockpit-296-1.el9.x86_64
libvirt-dbus-1.4.1-5.el9.x86_6
libvirt-client-9.3.0-2.el9.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Prepare a shutoff vm.
2. Click edit after memory, change the Maximum allocation to a bigger value by edit and save
3. Run the vm
4. Click edit after memory, change the Current allocation to a bigger value by edit and save.
The Memory won't change immediately.
5. Shutdown the vm, the memory value is changed to the value set in step4.
Actual results:
The Memory won't change immediately in step 4.
Expected results:
The memory change immediately for running vm when edit "Current allocation"
Additional info:
With old build like cockpit-machines-291-1.el9.noarch, it works fine.