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
vsphere: virtual_machine creation hangs on waiting for VM #7479
Comments
Experiencing the same issue with Terraform v0.6.16 and ESXi 6.0.0. The machine is created and is bootable.
terraform output
|
How does terraform verify the VM state? Does it rely on vmwaretools inside the guest? If so, do you have them installed? |
terraform 0.7.0_rc3 is working for me. I will investigate why in coming days. |
I can say, that for me it was related to 2 things:
|
I have the same issue with 0.7.0 I let the loop run for ~40 minutes. Even though the VM is in vSphere. I wouldn't think the VM would be required to have network for it to be created. In my infrastructure I need to take the MAC address from the created machine to assign an IP lease for the system. But I can't get the MAC address until the machine has been created. Is there a way to skip the IP check or a way to get details of the VM when the machine has not been verified to be up? I'm using skip_customization but still am not able to verify the machine has been created. |
is there a fix for this issue? im assigning a static ip address to a ubuntu vm (terraform .0.7.2/vsphere 6.0) the "still creating" loop stops after 10 minutes. can you please implement a timeout....cause the vm is already running after 4-5 minutes. the state detection does not work for whatever reason. |
+1 to this. Just spins and spins. vsphere_virtual_machine.laskotest1: Still creating... (1m40s elapsed) UPDATE: My problem is solved if I removed the second network_interface definition, and also only have a "label" definition. Otherwise I get the infinite loop. Once my VM has been cloned, I then have to run This is obviously not ideal and I don't know enough about Go to dive in and fix this. I do know enough about go to realize that is basically stalling on the fact that the interfaces don't have IP's and the network I'm connected to isn't going to be providing an IP via DHCP. The IP's are assigned by hand -- effectively the bug as I see it is that the current implementation requires that a Network interface exist, and also that the network interface have an IP otherwise it just sits spinning on the WaitForNetIP method forever. In a perfect world I presume that we should expect that the interface we are creating should have an IP, however, thats not always going to be the case -- Why hasn't a sensible timeout been set to at a minimum stop trying to wait after x seconds and continue on. |
+1 with v0.7.13 network_interface { vsphere_virtual_machine.newvm: Still creating... (2m50s elapsed) |
I am facing the same issue. Please help me to resolve this issue. Or please specify alternate solution for this scenario. Terraform file: { |
Trying to create hosts with two NICs where the first is the "management interface" that will receive a DHCP lease and the second is an interface used only as a bridge adapter, and does not receive an IP address. Is actual IP connectivity to all interfaces a requirement for the vsphere provider to succeed? |
Seems to be that every NIC with a mac-address needs an IP-adress: |
I guess finer control of this is required from govmomi. Updating the WaitForNetIp function from:
to:
will continue if there is more than 0 ips assigned. This at least allows terraform to complete in my "Multi-homed & bridge" scenario. |
The WaitForNetIP function has been updated in govmomi. |
Was this change already pushed? I have just updated to v0.9.2 and I still have this issue.. 2017/03/28 15:46:28 [DEBUG] dag/walk: vertex "meta.count-boundary (count boundary fixup)", waiting for: "vsphere_virtual_machine.vm" Is there any workaround for this issue? |
+1 I need a work around for this as well. Taking 10 minutes to even get to provisioning the vm. |
Is there anyone looking into this issue? Any ETA? |
Any updates? |
I am seeing this too, when running "terraform refresh" it gets stuck on "waiting for interfaces to appear" It only seems to happen on VMs that have been running for a while, and rebooting the VM seems to get it to go through for some reason... |
bpoland. I found rebooting the vm works as well.. Just dealt with this yesterday too.. |
I think this may be related to a reboot of virtualcenter. It seems like if vCenter is rebooted then all VMs deployed before the reboot encounter this issue. |
Sometimes I've found that a VM will just remain in a powered off state. If I manually start the machine, the terraform apply completes. It also seems that if an automatic migration is triggered on a new VM midway through the provisioning process, the process will fail. |
I too may have this issue , Terraform v0.11.10
|
Was facing the same issue but got resolved once I have added gateway and netmask. Below is the code for reference:
|
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. |
terraform-0.6.16
Terraform version: 0.7.0 rc2 46a0709
Example resource:
And it is waiting for ever:
At least I saw like 25 minutes waiting
When I abort run and try to re-run, I'm getting:
Can you point me if this is terraform issue or something with template, which I'm using.
And this
2016/07/04 17:22:15 [DEBUG] plugin: terraform: vsphere-provider (internal) 2016/07/04 17:22:15 [DEBUG] add cdroms: [] 2016/07/04 17:22:15 [DEBUG] plugin: terraform: vsphere-provider (internal) 2016/07/04 17:22:15 [DEBUG] VM customization skipped 2016/07/04 17:22:15 [DEBUG] plugin: terraform: vsphere-provider (internal) 2016/07/04 17:22:15 [INFO] Created virtual machine: Projects/terraform-test/terraform-web
is repeating from time to timeThe text was updated successfully, but these errors were encountered: