Bug 1569551

Summary: Auto-refresh values take forever to load values in dropdown
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: UI - ServiceAssignee: Chris Hale <chhale>
Status: CLOSED ERRATA QA Contact: Shveta <sshveta>
Severity: high Docs Contact:
Priority: high    
Version: 5.9.0CC: akarol, bascar, cpelland, dclarizi, lavenel, obarenbo
Target Milestone: GAKeywords: ZStream
Target Release: 5.9.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.9.2.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1568574 Environment:
Last Closed: 2018-05-07 20:49:42 UTC Type: ---
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: 1568574    
Bug Blocks:    

Comment 2 CFME Bot 2018-04-19 13:37:27 UTC
New commit detected on ManageIQ/manageiq-ui-service/gaprindashvili:

https://github.com/ManageIQ/manageiq-ui-service/commit/c482dfeec80d04c07563c50d2aad3ef327434276
commit c482dfeec80d04c07563c50d2aad3ef327434276
Author:     Allen Wight <allen.b.wight>
AuthorDate: Wed Apr 18 17:07:18 2018 -0400
Commit:     Allen Wight <allen.b.wight>
CommitDate: Wed Apr 18 17:07:18 2018 -0400

    Merge pull request #1423 from chalettu/custom-button-refresh-issue

    BZ#1568574 - Fixed issue with custom button details dynamic field refresh
    (cherry picked from commit 43580fc6e2e3126dd2e64d6899b2c162987eaefc)

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1569551

 client/app/states/services/custom_button_details/custom_button_details.state.js | 2 +-
 client/app/states/services/custom_button_details/custom_button_details.state.spec.js | 4 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

Comment 3 Shveta 2018-05-03 17:55:11 UTC
Fixed .
Verified in 5.9.2.4.20180501195858_35dc609

Comment 6 errata-xmlrpc 2018-05-07 20:49:42 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/RHSA-2018:1328