-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Assigning static IP to nodes - help! #7714
Comments
Has it got to do with adding more labels to this segment under the
|
Okay, so I added these lines to the
for each type of nodes respectively, but I still don't get the IPs as configured. Seemed to look fine when
But the output turns out different:
Am I missing something here? |
Output while apply
|
This would have been a really useful, even three years later. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Hi, so I have this problem using vSphere to apply terraform nodes and making the IP address static. I don't know why the IP address of the nodes keep jumping - causing errors here and there as I carry on building the infrastructure. I have tried changing the ifcfg-eno(xxx) file (am running on CentOS 7) but am unable to restart the system network. This only applies to the VMs created by
terraform apply.
Is there any other way to deploy the nodes with static IP addresses?
(am currently very new to this scene and would appreciate your help! sorry if I've missed out any relevant important information, will update asap!)
Terraform Version
0.6.16
Terraform Configuration Files
Debug Output
Expected Behavior
Able to restart network after editting ifcfg file to enable static IP addressing in place of dhcp
Actual Behavior
Unable to restart network
Steps to Reproduce
terraform get, plan, apply
systemctl restart network
The text was updated successfully, but these errors were encountered: