-
Notifications
You must be signed in to change notification settings - Fork 6
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
Pulumi failing to detect IP although successfully configured by cloud-init. #182
Comments
@mkennedy85 per hashicorp/terraform-provider-vsphere#718 (comment) (from the upstream provider) it seems that different OS's populate the IP address into different paths on the VM - Depending on that, it might be necessary to set |
@clstokes I did actually move ahead to configuring it with One thing to note is that it works if you use the default OVF datasource for guest customization, but using the guest info for user-data with cloud-init, seems to respond differently. I suspect there are cloud-init processes that take over, depending on the customization, and VMware tools is no longer sending info back to the processes that started the clone operation. I may be wrong, but this is a thought. |
I'm not sure this is a pulumi issue, I've had all sorts of problems doing this with terraform. You can solve it for a specific OS/template configuration with careful guestinfo settings, but I have not managed to build a generic VM provisioning system yet. Seems that a lot of the issues I had were because I wanted static IP addresses for my created VMs Here's my workflow just in case anyone finds this useful - there's obviously a bunch of underlying utility code not included here (for example the actual config data which is created using mako templates (python)) Import a standard Ubuntu OVA and enable guestinfo
Provision VMs from the above template
This eventually bubbles up into a top level Pulumi project for creating VMs to build a k8s cluster....
|
Hello!
Issue details
When cloning a VM and using the cloud-init DatasourceVMwareGuestinfo datasource, Pulumi is unable to detect that an IP has been successfully set and the network is up, so it never completes and returns the error:
This is not the case when using the OVF customization, as Pulumi reports that the VM has been configured and succeeds.
Steps to reproduce
pulumi up -y
Expected: Pulumi to complete successfully and provide the IP as an output.
Actual: The VM is configured as expected, but Pulumi does not return successfully due to not detecting that vmware-tools detects an IP. vSphere does successfully show an IP address in the vSphere UI, even before Pulumi fails, so it does appear that vmware-tools is getting an IP, but this is not being communicated back to Pulumi.
The text was updated successfully, but these errors were encountered: