Red Hat Bugzilla – Bug 1286843
Lost tenant dropdown entries in orchestration reconfiguration dialog
Last modified: 2016-06-29 11:14:05 EDT
Description of problem: Order an orchestration service for OpenStack provider with multiple tenants. Choose a non-default tenant. After the service completes, try to reconfigure the service. On the dialog the tenant shows <default> and is not changeable. What to expect is the tenant should be the one previously selected. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
There are two causes for the problem. Although the tenant selection does not look like a dropdown list, it is a disabled dynamic dropdown list. The script to provide entries to the dropdown does not work correctly for reconfiguration. Secondly, the UI does not set the selection to the previously set value. The UI issue has been tracked by https://bugzilla.redhat.com/show_bug.cgi?id=1285755. This BZ is to track the backend fix for the script to provide entries to the dropdown. The same problem is seen to other scripts to provision Azure related dynamic dropdown lists
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/f2d5092796985d2147bff0d79b4145b781f7a842 commit f2d5092796985d2147bff0d79b4145b781f7a842 Author: Bill Wei <bilwei@redhat.com> Date: Mon Nov 30 15:11:49 2015 -0500 Fix dynamic dropdown scripts for service reconfiguration
Created attachment 1157220 [details] Tenant list The reconfigure service does not show any field editable. All are read only fields .
The tenant field suppose to be read only. Once a stack is deployment, the reconfiguration can change only the parameters.
Verified in 5.6.0.6-beta2.5.20160511140943_ff75fb2
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/RHBA-2016:1348