RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 969066 - heat-cfn: Handle parameters with = in them
Summary: heat-cfn: Handle parameters with = in them
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RDO
Classification: Community
Component: openstack-heat
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact: Amit Ugol
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-30 15:04 UTC by Natale Vinto
Modified: 2014-06-05 09:48 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-16 10:29:06 UTC
Embargoed:

Attachments (Terms of Use)

Description Natale Vinto 2013-05-30 15:04:27 UTC 
Description of problem:

If parameters with "=" are used in heat-cfn creation an error is given due wrong string splitting


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


How reproducible:

heat-cfn create openshift --template-file=OpenShift.template --parameters="KeyName=${USER_KEY};DnsSecKey=A_STRING_WITH_==;UpstreamDNS=8.8.8.8"



Steps to Reproduce:
1.
2.
3.

Actual results:
ERROR:Failed to create. Got error:
ERROR:too many values to unpack


Expected results:
CREATE_IN_PROGRESS


Additional info:

Fixed in latest openstack/heat https://review.openstack.org/#/c/26772/
Comment 1 Natale Vinto 2013-05-30 15:06:02 UTC 
/usr/lib/python2.6/site-packages/heat/cfn_client/client.py affected line 140
Comment 2 Steven Hardy 2013-05-30 15:28:13 UTC 
Note the same issue exists in python-heatclient, so that will need to pull in the fix for https://bugs.launchpad.net/python-heatclient/+bug/1183842 when it gets merged.
Comment 3 Steven Hardy 2013-09-16 10:29:06 UTC 
This was fixed in 2013.2:

https://github.com/openstack/heat/commit/2d81dc9baad2459211d3493dcb91ab70de26aaf2

Note heat-cfn will not be part of the heat havana release, so the "heat" tool from the python-heatclient package should be used instead.
Note You need to log in before you can comment on or make changes to this bug.