Comma-delimited lists in heat template defaults are incorrectly populated into the launch form

Bug #1569145 reported by Donovan Jones
This bug affects 5 people
Affects Status Importance Assigned to Milestone

Bug Description

When using a heat template where OS::Neutron::Subnet dns_nameservers points at a yaml comma_delimited_list of nameservers eg:

    type: comma_delimited_list
    description: DNS servers for the private network
    default: [,, ]

    type: OS::Neutron::Subnet
      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 }
        - start: { get_param: private_net_pool_start }
          end: { get_param: private_net_pool_end }
      dns_nameservers: { get_param: private_net_dns_servers }

Config examples above from this heat template:

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'', u'', u'']

If this is run directly it results in these errors:

bug-test 5715a06f-af3c-43d7-ab9d-302527265ba3 0 minutes Create Failed Resource CREATE failed: BadRequest: resources.private_subnet: Invalid input for dns_nameservers. Reason: '[u' is not a valid nameserver. [u'' is not a valid IP or hostname. Details: '[u' is not a valid IP addr

This should be:,,

These errors have been confirmed using the latest upstream horizon code.

Tags: heat
Tolly Pan (tollypan)
no longer affects: openstack-user-stories
Akihiro Motoki (amotoki)
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
Revision history for this message
Akihiro Motoki (amotoki) wrote :

heat panel is split out to heat-dashboard. Retargeting to heat-dashboard.

affects: horizon → heat-dashboard
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.