Bug 1311308 - <Choose> Won't Display on Refresh of Dynamic Dropdown
<Choose> Won't Display on Refresh of Dynamic Dropdown
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS (Show other bugs)
Unspecified Unspecified
medium Severity medium
: GA
: 5.6.0
Assigned To: Martin Hradil
: ZStream
Depends On:
Blocks: 1312049
  Show dependency treegraph
Reported: 2016-02-23 16:42 EST by Dustin Boyd
Modified: 2016-07-12 14:45 EDT (History)
10 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1312049 (view as bug list)
Last Closed: 2016-06-29 11:39:14 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Dustin Boyd 2016-02-23 16:42:25 EST
Description of problem:
I have <Choose> set as a value if the hash is nil. <Choose> shows on initialization, but when it refreshes and redoes the ldapsearch, it goes to a blank value. The value <Choose> is in the hash in the logs when you log the inspect. I change the value to -Choose- and it is shows fine on the refresh without issues. I tried / \ REGEX escape values to no avail. It will escape and show the escape characters with the rest of the value.

Version-Release number of selected component (if applicable):

How reproducible:
Every time it refreshes after initialization.

Steps to Reproduce:
1. Create a dynamic dropdown with automate code that has <Choose> as the nil value of a hash
2. Create a service dialog to use this dynamic dropdown and have it set to auto refresh
3. Try to create a service with this dialog and allow it to auto refresh

Actual results:
Initializes 1x fine, but subsequent auto refreshes change the displayed value to blank.

Expected results:
The dynamic dropdown shows <Choose> as the default value when sorted alphabetically in the hash.

Additional info:
self_service UI shows the value fine, but the old Service Catalog doesn't display correctly.
Comment 3 Dustin Boyd 2016-02-24 14:52:48 EST
Dan, required is taken away when I select dynamic. I have dialog_field["required"] = "true" in the automate code. Do I have to set it ahead of time before I create the element like I do when it gives me the error of "cannot create without initial values" and then go back and make it dynamic?
Comment 4 Dustin Boyd 2016-02-24 15:02:52 EST
Dan, I changed it from dynamic to traditional and saved it with the true value. Changed it back to dynamic with the same automate code underneath. No change since I toggle it between dynamic to traditional and it appears false underneath the dynamic every time I toggle it. It seems like more of a < > issue than anything since I can put gnandndindand between < > and it's a blank value.
Comment 5 Harpreet Kataria 2016-02-25 09:52:17 EST

This issue appears to be fixed in commit 30e5964f0f7a461aecee5f7e6a06e07466f5b7f5 on upstream master, i am not sure if all the changes in that commit are safe to be cherry-picked on to 5.5.z so sending this ticket your way to cherry-pick changes appropriately. Let me know if you have questions.

Comment 7 Shveta 2016-04-19 14:00:49 EDT
Verified in
Comment 9 errata-xmlrpc 2016-06-29 11:39:14 EDT
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.


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