Bug 1371272 - unable to use {nil => "<default>"} with self provisioning when selecting dialog_tenant_name
Summary: unable to use {nil => "<default>"} with self provisioning when selecting dial...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Provisioning
Version: 5.6.0
Hardware: All
OS: All
unspecified
high
Target Milestone: GA
: 5.6.2
Assignee: Bill Wei
QA Contact: Shveta
URL:
Whiteboard:
Depends On: 1370502
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-29 18:07 UTC by Satoe Imaishi
Modified: 2022-07-09 07:53 UTC (History)
7 users (show)

Fixed In Version: 5.6.2.0
Doc Type: Bug Fix
Doc Text:
Previously, if there was no cloud tenant selected by the user, the backend expected the tenant_name to be nil. For the Self Service UI, since the options need to be passed through REST, nil was converted to an empty string. As a result, the {nil => "<default>"} value was unable to be used with self service provisioning when selecting dialog_tenant_name. This fix treats an empty string as no tenant option which has resolved the issue.
Clone Of: 1370502
Environment:
Last Closed: 2016-10-04 14:33:40 UTC
Category: ---
Cloudforms Team: Unknown
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1996 0 normal SHIPPED_LIVE Important: CFME 4.1 bug fixes and enhancement update 2016-10-04 18:26:13 UTC

Comment 2 Bill Wei 2016-08-31 13:42:27 UTC 
darga/yes
https://github.com/ManageIQ/manageiq/pull/10888
Comment 3 Oleg Barenboim 2016-09-01 00:41:43 UTC 
https://github.com/ManageIQ/manageiq/pull/10888 has been backported to Darga
Comment 4 Shveta 2016-09-16 16:13:16 UTC 
BLocked by https://bugzilla.redhat.com/show_bug.cgi?id=1376617
Comment 5 Shveta 2016-09-16 18:07:56 UTC 
Fixed.
Verified in 5.6.2.0.20160913114355_70e9086
Comment 7 errata-xmlrpc 2016-10-04 14:33:40 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://rhn.redhat.com/errata/RHSA-2016-1996.html
Note You need to log in before you can comment on or make changes to this bug.