Open danielhanlon opened 6 years ago
Following on from my own post, this seems to be consequence of incorrectly setting
aws.elastic_ip = "
rather than the IP address.
I had to remove the vagrant reference by deleting the dummy box and restarting, but after doing this and setting the elastic_ip configuration correctly I can use vagrant destroy as expected.
Thanks,
Daniel.
Hi,
Sorry if I'm asking about this in the wrong place, but I've had the following problem.
I have a vagrant initiated EC2 instance with an elastic IP. When I try to destroy the instance I get the error:
.../.vagrant.d/gems/2.4.3/gems/excon-0.60.0/lib/excon/middlewares/expects.rb:7:in `response_call': InvalidParameterValue => You must specify an association id when unmapping an address from a VPC instance (Fog::Compute::AWS::Error)
and the vagrant reference remains.
Any suggestions would be much appreciated as the plugin is very useful.