Comma-delimited lists in heat template defaults are incorrectly populated into the launch form
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
heat-dashboard |
New
|
Undecided
|
Unassigned |
Bug Description
When using a heat template where OS::Neutron::Subnet dns_nameservers points at a yaml comma_delimited
private_
type: comma_delimited
description: DNS servers for the private network
default: [ 202.78.247.197, 202.78.247.198, 202.78.247.199 ]
private_subnet:
type: OS::Neutron::Subnet
properties:
name: { get_param: private_subnet_name }
network_id: { get_resource: private_net }
cidr: { get_param: private_net_cidr }
gateway_ip: { get_param: private_net_gateway }
allocatio
- start: { get_param: private_
end: { get_param: private_
dns_
Config examples above from this heat template: https:/
When the template above is loaded either by direct url or from a file the launch stack form is populated from the template provided. The form field is populated with the following content:
[u'202.78.247.197', u'202.78.247.198', u'202.78.247.199']
If this is run directly it results in these errors:
bug-test 5715a06f-
This should be:
202.78.
These errors have been confirmed using the latest upstream horizon code.
no longer affects: | openstack-user-stories |
tags: | added: heat |
summary: |
- Launch stack fails when heat template includes OS::Neutron::Subnet with - a list of nameservers + Comma-delimited lists in heat template defaults are incorrectly + populated into the launch form |
heat panel is split out to heat-dashboard. Retargeting to heat-dashboard.