FloatingIPAssociation problem in Mitaka

[Mika Oksanen]

a heat template which creates a network, server and allocates + associates a floating ip to server interface don't work in Mitaka 9.0.
Same template tested in Liberty and Kilo without errors.

mitaka_ipassociation.yaml
heat_template_version: 2015-04-30

parameters:
  Public:
    type: string
    default: 'admin_floating_net'
    description: Public net
  Image:
    type: string
    default: 'TestVM'

resources:
  My_net:
    type: OS::Neutron::Net
    properties:
      name: My_net

  My_subnet:
    type: OS::Neutron::Subnet
    properties:
      name: My_subnet
      cidr: 192.168.1.0/24
      network: {get_resource: My_net}

  My_router:
    type: OS::Neutron::Router
    properties:
      name: My_router
      distributed: false
      external_gateway_info:
        network: {get_param: Public}

  My_router_interface:
    type: OS::Neutron::RouterInterface
    properties:
      router: {get_resource: My_router}
      subnet: {get_resource: My_subnet}

  My_port:
    type: OS::Neutron::Port
    properties:
      name: My_port
      network: { get_resource: My_net }

  Server:
    type: OS::Nova::Server
    properties:
      name: MyServer
      image: {get_param: Image}
      flavor: m1.medium
      networks:
        - port: { get_resource: My_port }
      availability_zone: nova

  My-IP:
    type: OS::Neutron::FloatingIP
    properties:
      floating_network: { get_param: Public }

  My-IP-Association:
    type: OS::Neutron::FloatingIPAssociation
    properties:
      floatingip_id: { get_resource: My-IP }
      port_id: { get_resource: My_port }

steps to reproduce:
Note. The command must be run as an Admin because router operations seems to require it.
(OS_PROJECT_NAME=admin, OS_USERNAME=admin etc)
heat stack-create mystack -f mitaka_ipassociation.yaml --poll

ERROR: The server could not comply with the request since it is either malformed or otherwise incorrect.
The error "ERROR heat.common.wsgi " <clip> "Exception handling resource: 'NoneType' object is not iterable" might have something to do with this problem.

Seems that there is a parsing problem.

If the My-IP-Association block is commented out then stack will be created.
The association can be done successfully later e.g. from Horizon

[Dmitriy (duvarenkov)]

Corresponding patch is merged in master https://review.openstack.org/#/c/350029/
Now waiting for merge sync with MOS.

[Dmitriy (duvarenkov)]

https://review.fuel-infra.org/#/c/25328/ patch fixing this issue is merged in MOS.

[Alexander Nagovitsyn (gluk12189)]

on verification

[Alexander Nagovitsyn (gluk12189)]

verified on snapshots/9.0-2016-09-12-132321