Bug 1538529

Summary: The "Save Changes" button should be disabled when there are no changes to save
Product: Red Hat OpenStack Reporter: Udi Kalifon <ukalifon>
Component: openstack-tripleo-uiAssignee: Jiri Tomasek <jtomasek>
Status: CLOSED ERRATA QA Contact: Udi Kalifon <ukalifon>
Severity: medium Docs Contact:
Priority: medium    
Version: 12.0 (Pike)CC: apannu, jjoyce, jpichon, jrist, jschluet, slinaber, tvignaud
Target Milestone: betaKeywords: Triaged
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-ui-8.3.1-0.20180303225336.57e3d96.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-27 13:43:23 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 Udi Kalifon 2018-01-25 08:56:12 UTC
Description of problem:
In the edit role dialog, the "Save Changes" button is initially enabled even though the user hasn't yet entered any changes and there is nothing to save. It also remains enabled after the 1st save, and only after the 2nd save it becomes disabled.


Version-Release number of selected component (if applicable):
openstack-tripleo-ui-7.4.3-4.el7ost.noarch


How reproducible:
100%


Steps to Reproduce:
1. Edit a role
2. Notice that the "Save Changes" button is initially enabled
3. Change a setting (for example the flavor) and save
4. The "Save Changes" button is still enabled right after the save, as if the changes were not really saved
5. Click "Save Changes" again


Actual results:
The "Save Changes" button becomes disabled only after the 2nd save

Comment 6 Udi Kalifon 2018-04-09 12:39:53 UTC
Verified in: openstack-tripleo-ui-8.3.1-2.el7ost.noarch

Comment 8 errata-xmlrpc 2018-06-27 13:43:23 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, 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/RHEA-2018:2086