Description of problem: Since upgrade to version 3.2 (following https://access.redhat.com/articles/1435433), the Refresh button on my Dynamic Dropdown Lists runs the method but do not update the UI that hangs with the waiting wheel. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Create a custom dialog with a Dynamic Dropdown List and a Refresh button 2. Create a method that is call when hiting refresh 3. Call the dialog from a service provisioning or custom button 4. Click on "Refresh" Actual results: The UI hangs. Expected results: The UI is refreshed with the "dialog_field" generate in the method. Additional info: Might be linked to this bug : https://bugzilla.redhat.com/show_bug.cgi?id=1235259
Same behaviour with ManageIQ botvinnik-1.20150625120628_eb92001.
Blocker and High priority. QE to replicate.
New commit detected on cfme/5.4.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=6222cb030f20afa892d4490c964ec3bbcfae2b7f commit 6222cb030f20afa892d4490c964ec3bbcfae2b7f Merge: 9b3a471 5afe1a5 Author: Greg McCullough <gmccullo> AuthorDate: Mon Jun 29 17:19:40 2015 -0400 Commit: Greg McCullough <gmccullo> CommitDate: Mon Jun 29 17:19:40 2015 -0400 Merge branch 'bz1236522' into '5.4.z' BZ1236522 - Fix refresh button on dynamic drop down dialogs Cherry-picked from this PR: https://github.com/ManageIQ/manageiq/pull/2971/ Cherry-pick was completely clean. https://bugzilla.redhat.com/show_bug.cgi?id=1236522 See merge request !149 .../application_controller/dialog_runner.rb | 12 ++++- vmdb/app/helpers/application_helper/dialogs.rb | 2 +- vmdb/app/models/dialog_field_drop_down_list.rb | 2 +- .../dialogs/_dialog_field_drop_down_list.haml | 18 ++++---- .../shared/dialogs/_dialog_field_radio_button.haml | 6 +-- .../helpers/application_helper/dialogs_spec.rb | 4 +- .../models/dialog_field_drop_down_list_spec.rb | 52 ++++++++++++++++++++++ 7 files changed, 80 insertions(+), 16 deletions(-)
*** Bug 1236018 has been marked as a duplicate of this bug. ***
No, that's the cloned one for a different target release. This one is for the latest upstream build, whereas that one is for 5.4.z
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-2015:2551