Red Hat Bugzilla – Bug 1420555
Service dialog dropdown differs from what is processed by service request
Last modified: 2017-02-27 14:31:25 EST
Service UI PR: https://github.com/ManageIQ/manageiq-ui-service/pull/512
Main repo PR: https://github.com/ManageIQ/manageiq/pull/13778
Oops, that link in comment 3 should say "Darga backport for main repo PR". Darga backport for SUI: https://github.com/ManageIQ/manageiq-ui-service/pull/513 And as of this comment, that Darga backport for SUI hasn't been merged, so moving this back to ON_DEV instead of POST.
This BZ is for 5.7.z, so no need to wait for Darga backport.
Correct parameters are processed in 5.7.1.2.20170214162958_ebaba61
New commit detected on ManageIQ/manageiq/euwe: https://github.com/ManageIQ/manageiq/commit/b89f5b59f03b5df59fd13e5f82251bc3bb784c55 commit b89f5b59f03b5df59fd13e5f82251bc3bb784c55 Author: Erik Clarizio <eclarizio@gmail.com> AuthorDate: Mon Feb 20 09:28:08 2017 -0800 Commit: Erik Clarizio <eclarizi@redhat.com> CommitDate: Tue Feb 21 07:40:18 2017 -0800 Force triggering of fields set to auto-refresh https://bugzilla.redhat.com/show_bug.cgi?id=1420555 app/helpers/application_helper/dialogs.rb | 4 ++++ app/views/shared/dialogs/_dialog_field_check_box.html.haml | 4 +++- .../dialogs/_dialog_field_date_and_date_time_control.html.haml | 4 +++- app/views/shared/dialogs/_dialog_field_drop_down_list.html.haml | 4 +++- app/views/shared/dialogs/_dialog_field_radio_button.html.haml | 4 +++- app/views/shared/dialogs/_dialog_field_text_area_box.html.haml | 4 +++- app/views/shared/dialogs/_dialog_field_text_box.html.haml | 4 +++- spec/helpers/application_helper/dialogs_spec.rb | 8 ++++++++ 8 files changed, 30 insertions(+), 6 deletions(-)
New PRs Classic UI - https://github.com/ManageIQ/manageiq/pull/13994 Service UI - https://github.com/ManageIQ/manageiq-ui-service/pull/524
Values are refreshed in dynamic drop downs . With the attached dialog and automate method . selecting value in first drop down refreshed values in location (second) Verified in 5.7.1.3.20170221135006_818f133
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://rhn.redhat.com/errata/RHSA-2017-0320.html