Bug 2225089

Summary:	[Machines] Can not edit "Maximum allocation" by dragging the slider
Product:	Red Hat Enterprise Linux 9	Reporter:	Xianghua Chen <xchen>
Component:	cockpit-machines	Assignee:	Nobody <nobody>
Status:	CLOSED ERRATA	QA Contact:	Xianghua Chen <xchen>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	9.3	CC:	kkoukiou, mpitt, qzhang, wshi, ymao, yunyang
Target Milestone:	rc	Keywords:	Regression, Triaged
Target Release:	9.3	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cockpit-machines-295-1.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-11-07 08:24:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Xianghua Chen 2023-07-24 09:53:11 UTC

[Machines] Can not edit "Maximum allocation" by dragging the slider

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" by draging the slider
The Maxmium value does not change and no changes after save too.

3. Input a larger value by edit the "Maximum allocation" value directly, save.
Re-open edit, click the slider, the  "Maximum allocation" value will change to default value again.



Actual results:
See step 2 & step 3.



Expected results:
The Maxmium value of Memory should change by dragging slider and take effect after save.

And clicking slider won't change the value to default value.



Additional info:

Comment 1 Martin Pitt 2023-07-25 03:49:47 UTC

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

Comment 4 Xianghua Chen 2023-08-02 02:30:08 UTC

Verified with packages:
cockpit-machines-295-1.el9.noarch
cockpit-296-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 shutoff vm.

2. Click "edit" after memory, change the "Maximum allocation" by draging the slider
The Maxmium value can change and  changes take effect after save .

3. Input a larger value by edit the "Maximum allocation" value directly, save.
Re-open edit, click the slider, the  "Maximum allocation" value does not change to default value again.

So verified.

Comment 7 errata-xmlrpc 2023-11-07 08:24:53 UTC

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