Bug 1497678 - Role configuration is fast for the first role, then takes really long for the other roles
Summary: Role configuration is fast for the first role, then takes really long for the...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-ui
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: Upstream M3
: 14.0 (Rocky)
Assignee: Jiri Tomasek
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-02 12:47 UTC by Udi Kalifon
Modified: 2019-01-11 11:48 UTC (History)
6 users (show)

Fixed In Version: openstack-tripleo-ui-9.3.1-0.20180921180341.df30b55.el7ost.noarch.rpm
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-11 11:48:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 525672 0 None None None 2018-02-06 13:35:46 UTC
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:48:38 UTC

Description Udi Kalifon 2017-10-02 12:47:38 UTC
Description of problem:
In the GUI, when changing the role configuration (for example setting OvercloudControllerFlavor to "control") and hitting "Save Changes" - you wait only a short second for the changes to be saved for the first role, but wait about 1 minute for saving the configurations of the next roles you edit.

If you press F5 and edit another role you'll also wait only a short second for the first role you edit, and for the other roles after that you'll wait a long time.


Version-Release number of selected component (if applicable):
openstack-tripleo-ui-7.4.1-0.20170925201442.2bb5965.el7ost.noarch


How reproducible:
100%


Steps to Reproduce:
1. Edit the Controller role, for example, and change it's flavor from "baremetal" to "control"
2. Save Changes and close the dialog
3. Edit another role and change it's flavor appropriately
4. Save Changes


Actual results:
The 2nd save changes takes really long, compared to almost no time at all for the 1st change.


Expected results:
Saving the configuration changes should always be fast.

Comment 1 Jiri Tomasek 2017-10-11 11:50:01 UTC
Are you sure that saving the parameters takes that long? The subsequent loading of the parameters takes quite long due to parameters cashing - fetching parameters takes short time untill there has been changes made, after the changes to parameters were made, it takes longer to load parameters again as the parameters cache is invalid and deployment plan needs to be processed by Heat to get up to date parameters.

Do you have an environment I could use to verify the problem, please?

Comment 2 Udi Kalifon 2017-10-15 11:52:27 UTC
It's the saving that takes long, not the fetching after that. Ping me when you have time an I'll let you see it on my environment.

Comment 3 Jiri Tomasek 2018-02-06 13:35:46 UTC
Updating of deployment parameters has changed recently so heat validation is run every time parameters are updated. The behaviour described in bug report is not happening any more. Updating parameters take long due to heat validation unfortunately.

Comment 4 Udi Kalifon 2018-02-08 10:45:46 UTC
This doesn't happen any more on OSP12 z1. Should we mark this VERIFIED, or why is it still ON_DEV? Thanks.

Comment 5 Jiri Tomasek 2018-02-20 10:06:59 UTC
It is on_dev because the patch assigned to this is still pending merge. If you confirm that this is fixed and can't get reproduced any more, then fine, lets move it to verified.

Comment 6 Udi Kalifon 2018-02-20 12:34:28 UTC
I'll verify again after the patch is merged, to be on the safe side.

Comment 10 Udi Kalifon 2018-11-07 16:58:50 UTC
Same performance for all roles now. Verified: openstack-tripleo-ui-9.3.1-0.20180921180342.df30b55.el7ost.noarch

Comment 12 errata-xmlrpc 2019-01-11 11:48:07 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


Note You need to log in before you can comment on or make changes to this bug.