Hide Forgot
Description of problem: When clicking "Save Changes" in the configuration dialog, you get a success message but the dialog doesn't close and the changes you made are not saved. You have to press "Cancel" to close the dialog and there is no way to enable environment files. No errors are seen in the console. This is currently a blocker for the testing. Version-Release number of selected component (if applicable): openstack-tripleo-ui-2.0.1-0.20170126144317.f3bd97e.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Click on "Edit Configuration" to open the deployment configuration dialog 2. Enable some environment files, for example storage 3. Save changes Actual results: The dialog doesn't close Expected results: Changes should be saved, the dialog should be closed.
Using the 11.0-20170308.1.el7ost puddle, and latest upstream, I cannot reproduce this issue. Selecting the storage environment, and clicking "save" shows a success notification. The selection is properly persistent between page reloads. Note that I don't believe the dialog is to close upon successful save. You are and should be able to continue editing the properties of the plan once you save. There are errors in the javascript console. Are there any errors in your console?
This bug still recreates downstream with the latest puddle (2017-03-15) and it's a blocker for the automation. There are no errors in the console.
I propose to solve this by adding another button to the dialog. We will then have two buttons for saving: "Save" and "Save and close".
Seconded
upstream fix proposed - waiting for reviews
while in review, this should be on_dev
https://review.openstack.org/#/c/451987/ merged
"Save and Close" button on parameters tab is missing openstack-tripleo-ui-3.1.0-8.el7ost.noarch
https://review.openstack.org/#/c/455462/ merged
Verified in 2017-04-24.2
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-2017:1245