ipassociation heat stack delete

[Kevin Fox]

We have a heat template we created that takes in an ip address as a param and then associates it with the vm created by the stack.

We have a stack running based on this, and we moved the floating ip address to a different host outside of heat.

When we then go and delete the heat stack, it fails to delete complaining the ip is associated with a vm other then the one it thinks it should be.

It should ignore the detach in this case and simply continue on with the deletion of the stack.

This is a liberty rdo on centos7 heat.

[Peter Razumovsky (prazumovsky)]

Do you use FloatingIPAssociation for associate ip to vm? Or I miss something?

[huangsm (huangsm)]

I have create stack from yaml files such as:

heat_template_version: 2015-04-30

resources:
  floating:
    type: OS::Neutron::FloatingIP
    properties:
      floating_network: Ext-Net
  port:
    type: OS::Neutron::Port
    properties:
        network: d476830c-161c-4c69-a079-5408a21c6f90
  instance:
    type: OS::Nova::Server
    properties:
      flavor: m1.tiny
      image: cirros
      metadata:
        source: heat
      networks:
        - floating_ip: {get_resource: floating}
          network: d476830c-161c-4c69-a079-5408a21c6f90
          port: {get_resource: port}

and

heat_template_version: 2015-04-30

resources:
  floating:
    type: OS::Neutron::FloatingIP
    properties:
      floating_network: Ext-Net
  instance:
    type: OS::Nova::Server
    properties:
      flavor: m1.tiny
      image: cirros
      metadata:
        source: heat
      networks:
         - network: d476830c-161c-4c69-a079-5408a21c6f90
  port:
    type: OS::Neutron::Port
    properties:
        network: d476830c-161c-4c69-a079-5408a21c6f90
  association:
    type: OS::FloatingIPAssociation
    properties:
      floatingip_id: {get_resource: floating}
      port_id: {get_resource: port}

And it's reproduced.
Can you show your template?

[huangsm (huangsm)]

And it is not reproduced.