# Want EIP to move uncondtionally

**URL:** <https://forum.ansible.com/t/want-eip-to-move-uncondtionally/20528>\
**Category:** Ansible Project\
**Created:** [February 11, 2016, 4:07am UTC](https://forum.ansible.com/t/want-eip-to-move-uncondtionally/20528 "2016-02-11T04:07:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shaun\_Brady](https://avatars.discourse-cdn.com/v4/letter/s/a88e4f/32.png) [@Shaun\_Brady](https://forum.ansible.com/u/Shaun_Brady)\
**Post date:** [February 11, 2016, 4:07am UTC](https://forum.ansible.com/t/want-eip-to-move-uncondtionally/20528/1 "2016-02-11T04:07:35Z")

</div>

Hello,  
Previously I had a playbook that would create an instance and associate an EIP  
with it. If this EIP was on another host, it would just be moved. I now get:

`Resource.AlreadyAssociated`  
resource eipalloc-d26705b6 is already associated with associate-id eipassoc-f7bf1d8f  
693c1800-0a6d-4af4-9587-3f715fd8bd8c

I believe the change is moving from EC2-Classic to VPC. If I just try use  
ec2\_eip to disassociate the address, I need to provide the instance id it is  
currently associated with. I don’t see a straight forward way to look up this  
instance, as 1) I’m already in a play connected to a host, but more importantly  
2) I don’t know if the host is up.

Is there a method I’m missing to say “disassociate this regardless of its  
current status”, or to easily look up the instance associated with the EIP?

For reference we are still on 1.9, but if the answer is in 2.0, that is in our  
future.

Thanks!

Shaun Brady  
Senior Web Services Engineer  
Nimbis Services, Inc.