Default value fields not properly populating when loading Heat templates from file through dashboard.

[Alberto Laporte]

Greetings,

This appears to be a minor but it appears to be an issue that can be replicated on both Liberty and Mitaka environments.

Environment details

Liberty: Horizon(8.0.2.dev34)
Mitaka: Horizon(9.1.1.dev6)

Issue observed: Loading a heat template with default values defined through the Horizon dashboard does not load all values as intended. With the sample template provided below [1] the key_name default value is populated, however instance_flavor, and instance_image values are not loading the default values as specified on the template.

[1]

heat_template_version: 2014-10-16

description: Launch groups of VMs.

parameters:
  key_name:
    description: Name of an existing PublicKey to enable SSH access to the instances.
    type: string
    default: user-key
    constraints:
       - custom_constraint: nova.keypair
  instance_flavor:
    description: VM Flavor
    type: string
    default: m1.small
    constraints:
       - custom_constraint: nova.flavor
  instance_image:
    description: VM Image
    type: string
    default: cirros
    constraints:
       - custom_constraint: glance.image
  num_vms:
    description: Number of Virtual Machines to launch
    type: string
    constraints:
      - allowed_values: [ "1","2","3","4","5","6","7","8","9","10","11","12","13","14","15","16","17","18","19","20" ]
  admin_password:
    description: Admin password for the new VMs
    type: string
    default: grannydont
  availability_zone:
    type: string
    description: The Availability Zone to launch the instance. Make sure to select the availability zone corresponding to your tenant

resources:
  machines:
    type: OS::Heat::ResourceGroup
    properties:
      count: { get_param: num_vms }
      resource_def:
        type: OS::Nova::Server
        properties:
          flavor: { get_param: instance_flavor }
          image: { get_param: instance_image }
          name:
             str_replace:
                template:
                   $name$index
                params:
                   $name: { get_param: "OS::stack_name" }
                   $index: "%index%"
          key_name: { get_param: key_name }
          admin_pass: { get_param: admin_password }
          admin_user: root
          availability_zone : {get_param: availability_zone}

outputs:
   instance_ip:
      description: The IP addresses of the deployed instance
      value: { get_attr: [machines, first_address] }

[Akihiro Motoki (amotoki)]

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

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/heat-dashboard 8.0.0.0rc1 release candidate.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/heat-dashboard 5.0.1 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/heat-dashboard 6.0.1 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/heat-dashboard 7.0.1 release.