-
Notifications
You must be signed in to change notification settings - Fork 124
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
sysprep_timeout is waiting for customization to complete, but then bootstrapping is happening with a different IP #420
Comments
Hi, if memory serves the timeout is the max time we'll wait, not a forced delay. How's it getting a different IP address? Ideally the template will boot up with no address at all.
|
Hi Swel, |
Do you have dynamic DNS? We also have |
I don't think we have dynamic DNS. And my bootstrap operation fails when we use hostname because my workstation can only find the hostname if it has an entry for that newly built vm in /etc/hosts. So as of now I have factored my command into three sections.
|
Hi, most of what we do at my job is DHCP and the bootstrapping works well. Instead of passing in an address use Still a bit puzzled as to what's going on with your template. I'll ask around the office -- I wasn't the one that made the Windows template so if I can get some pointers I'll pass them along. |
Yeah, we have used the dhcp option earlier as well but with this current issue being in place,just wanted to know whether this would cause any problems. |
Versions:
Platform Details
Scenario:
Trying to spin up the VM and bootstrap it using the following command
knife vsphere vm clone testVM3 --dest-folder Chef_Test --template NewTemplate -f Chef_Test --datastore my_datastore --cips 10.0.0.1/23 --cdnsips 10.0.0.2,10.10.0.3 --cspec win12 --start --sysprep_timeout 360 --bootstrap --winrm-user Adminstrator --winrm-password mypassword
As per the above command the VM is built successfully along with the Ip address and dns settings. However before it could bootstrap I want it to wait for 6 minutes using the sysprep_timeout in order for the customization to complete so that the bootstrap operation can take the correct IP address of the virtual machine.
But in this case the sysprep time started once the vm is cloned and powered on, but instead of waiting for 6 minutes via sysprep, the command went to bootstrap the machine right after the customization is complete.
My vcenter is a bit slow so that it is taking around 30 seconds for the actual Ip to reflect on the Vsphere UI once the cspec customizations are applied. So I want my vm clone command to wait for those 6 minutes irrespective of customization completion, so that it can take the correct IP address of the VM before proceeding with bootstrap.
Please paste the command and output (run with
-VV
). Don't forget to X out any passwords or sensitive information:Expected Result:
Sysprep to wait for the mentioned timeout seconds and then proceed with bootstrap
Actual Result:
Bootstrap process initiated right after cspecs are applied
The text was updated successfully, but these errors were encountered: