Bug 2217341

Summary:	[machines] The memory setting dialog could not be closed after clicking "Save"
Product:	Red Hat Enterprise Linux 8	Reporter:	YunmingYang <yunyang>
Component:	cockpit-appstream	Assignee:	Simon Kobyda <skobyda>
Status:	CLOSED MIGRATED	QA Contact:	YunmingYang <yunyang>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.9	CC:	jscotka, kkoukiou, mpitt, qzhang, wshi, xchen, ymao
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-15 14:14:32 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 YunmingYang 2023-06-26 06:17:42 UTC

Description of problem:
In a closed VM detail page, when setting the memory, change "Maximum allocation" to not "128MB" firstly. Then, re-open the setting dialog, and set "Maximum allocation" to "128MB", the dialog could not be closed after clicking "Save"

Version-Release number of selected components (if applicable):
cockpit-machines-292-1.el8.noarch
cockpit-292-1.el8.x86_64
libvirt-dbus-1.3.0-2.module+el8.8.0+16781+9f4724c2.x86_64

How reproducible:
100%

Steps to Reproduce:
1 Create a closed VM, then enter the VM detail page
2 Change "Maximum allocation" to not "128MB" firstly
3 Re-open the setting dialog, and set "Maximum allocation" to "128MB",

Actual results:
1 After step 3, the dialog could not be closed

Expected results:
1 After step 3, the dialog could be closed

Additional info:

Comment 1 RHEL Program Management 2023-09-15 14:13:13 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 2 RHEL Program Management 2023-09-15 14:14:32 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.