-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
alicloud_eip_association fails when instance has a public IP #597
Comments
Just a note, I've also opened an issue with the Ansible provisioner about |
Any help on this? |
HI @jakubgs EIP does not support association with a ECS instance with public ip. If you want to do it, please release the instance public ip firstly. |
Yes, but I need the public IP in order to provision the host from terraform. |
Modifying internet_max_bandwidth_out to 0 can remove the public ip. |
I see. So I'd have to copy the exact same |
Is there a way to do this without having to run Terrafomr twice? This really breaks the workflow. I don't see how I can in the same
Is it even possible? |
Okay, I've managed to make this work by setting |
Create a instance without public ip and attach a eip for it and then add the provisioner block with EIP is the best pratice. |
@jakubgs I will close this issue and if you still have problems, please reopen it. |
When trying to attach an
alicloud_eip
usingalicloud_eip_association
the following error is given:Now, this error is referring to the fact that one cannot attach an Elastic IP to an instance that already has a Public IP:
https://www.alibabacloud.com/help/doc-detail/72125.htm
An instance receives a Public IP when the
internet_max_bandwidth_out
parameter is set to a value greater than zero. One cannot provision an instance using theprovisioner
seciton if the instance does not have a public IP. In order to make that work I've been adding the following section to myalicloud_instance
config:My question is following:
How can I provision an
alicloud_instance
if it lacks a Public IP because I want to attach an Elastic IP to it afterwards?Am I missing something? How can I both provision a new instance and then attach an Elastic IP?
The text was updated successfully, but these errors were encountered: