Bug 1567621

Summary: The "Save" button doesn't appear after changing the deployment counters for the 1st time
Product: Red Hat OpenStack Reporter: Udi Kalifon <ukalifon>
Component: openstack-tripleo-uiAssignee: Jiri Tomasek <jtomasek>
Status: CLOSED ERRATA QA Contact: Udi Kalifon <ukalifon>
Severity: urgent Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: augol, beth.white, jjoyce, jrist, jschluet, jtomasek, lsurette, slinaber, tvignaud, ukalifon
Target Milestone: Upstream M3Keywords: Triaged
Target Release: 14.0 (Rocky)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-ui-9.1.1-0.20180710115855.7dd171e.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1620160 (view as bug list) Environment:
Last Closed: 2019-01-11 11:49:31 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:
Bug Depends On:    
Bug Blocks: 1620160    
Attachments:
Description Flags
Proposed error message to clarify the situation none

Description Udi Kalifon 2018-04-15 14:49:15 UTC
Description of problem:
After uploading a new plan and increasing the controllers count to 3, you can't save the changes. The "Manage Roles" button is still displayed. Only after updating more counters do you get the "Save" and "Cancel" buttons.


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


How reproducible:
100%


Steps to Reproduce:
1. Upload a new plan and browse to its deployment page
2. Edit the "Controller" role and set its flavor to "control"
3. Save and close the role editing dialog
4. Update the controller count to 3
5. See if you can save the changes...


Actual results:
No "Save" button


Expected results:
The "Save" and "Cancel" buttons should appear, and the "Manage Roles" button should disappear.


Additional info:
After updating the compute role and counters the problem is resolved.

Comment 1 Jason E. Rist 2018-04-25 14:57:24 UTC
Please attach the plan you used.

Comment 2 Jiri Tomasek 2018-04-25 15:09:01 UTC
I am going to investigate further, but the button should appear in case when the nodes assignment form (the counters) is valid && dirty && !submitting. Was one of the counters red? I assume that when you create plan initially, the controller and compute counts are set to 1. In case when there are no nodes ready yet, both are red so until one of the counts are red the save button will not appear.

Comment 3 Udi Kalifon 2018-05-08 14:22:15 UTC
The plan is just the default plan which you can create with:
tar -czf plan.tgz -C /usr/share/openstack-tripleo-heat-templates/ .

Jiri, you are also right. When the plan is new you have to configure the flavors for both the controller role and the compute role, and until then the counters are red. After configuring the 2nd role you get the save button. Is there a way to make it more clear to the user?

Comment 4 Jiri Tomasek 2018-05-09 12:47:37 UTC
Created attachment 1433806 [details]
Proposed error message to clarify the situation

Comment 5 Jiri Tomasek 2018-05-09 12:47:57 UTC
@Udi: We can provide an error message describing the situation. Would that be sufficient/helpful? (See attachment)

Comment 6 Udi Kalifon 2018-05-09 13:57:18 UTC
A message describing the problem can help a lot. For example, if the user changes a counter - check if other counters are red and display something telling the user that the changes will only be savable when all counters are valid.

Comment 7 Jason E. Rist 2018-05-09 14:37:37 UTC
Liz can you help with the proposed error message linked here
https://bugzilla.redhat.com/attachment.cgi?id=1433806

Comment 9 Liz 2018-05-21 14:52:44 UTC
Commented on the patch upstream with suggestion...
https://review.openstack.org/#/c/567221/

Comment 16 Udi Kalifon 2018-10-18 12:07:00 UTC
Verified in openstack-tripleo-ui-9.3.1-0.20180921180341.df30b55.el7ost.noarch

Comment 20 errata-xmlrpc 2019-01-11 11:49:31 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-2019:0045