Back to bug 1371272

Who When What Removed Added
Satoe Imaishi 2016-08-29 18:07:26 UTC Depends On 1370502
Bill Wei 2016-08-31 13:42:27 UTC Status ASSIGNED ON_DEV
Bill Wei 2016-09-01 13:54:49 UTC Status ON_DEV POST
Satoe Imaishi 2016-09-01 15:19:50 UTC Status POST MODIFIED
Marianne Feifer 2016-09-08 19:31:21 UTC CC mfeifer
Doc Text Cause: If there is no user selected cloud tenant, the backend expect the tenant_name to be nil. For SSUI since the options need to be passed through REST, nil was converted to an empty string.

Consequence: unable to use {nil => "<default>"} with self provisioning when selecting dialog_tenant_name

Fix: The fix is to treat an empty string as no tenant option.



Result:
Doc Type If docs needed, set a value Bug Fix
Satoe Imaishi 2016-09-13 20:32:08 UTC Status MODIFIED ON_QA
Fixed In Version 5.6.2.0
Dave Johnson 2016-09-14 03:06:02 UTC QA Contact dajohnso sshveta
Shveta 2016-09-16 18:07:56 UTC Status ON_QA VERIFIED
Suyog Sainkar 2016-09-30 06:14:52 UTC CC ssainkar
Cloudforms Team --- Other
Doc Text Cause: If there is no user selected cloud tenant, the backend expect the tenant_name to be nil. For SSUI since the options need to be passed through REST, nil was converted to an empty string.

Consequence: unable to use {nil => "<default>"} with self provisioning when selecting dialog_tenant_name

Fix: The fix is to treat an empty string as no tenant option.



Result:
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.
errata-xmlrpc 2016-10-04 04:40:52 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-10-04 14:33:40 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-10-04 10:33:40 UTC

Back to bug 1371272