Bug 2226968 - [Machines] Change "Current allocation" won't take effect immediately for running vm
Summary: [Machines] Change "Current allocation" won't take effect immediately for runn...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: cockpit-machines
Version: 9.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Simon Kobyda
QA Contact: Xianghua Chen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-27 07:48 UTC by Xianghua Chen
Modified: 2023-08-02 03:09 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-02 03:08:57 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-163647 0 None None None 2023-07-27 07:50:30 UTC

Description Xianghua Chen 2023-07-27 07:48:36 UTC
[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.

Comment 1 Xianghua Chen 2023-08-02 03:08:57 UTC
Can't reproduce it anymore, close as not a bug.


Note You need to log in before you can comment on or make changes to this bug.