You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Packer 1.7.2 fails to connect via SSH during the installation of an Ubuntu 20.04.2 live server because the ip of the guest changes after the first reboot, and the DHCP provides a different ip address. Packer still uses the first seen ip address.
In #8528 , it's claimed that this point is fixed for vmware-iso, but I'm witnessing that with vsphere-iso, the issue remains.
Reproduction Steps
Use packer 1.7.2 with vsphere-iso
Set up a deployment of an Ubuntu 20.04.2 live server (thus, not the legacy one)
The installation looks good, but the logs are showing Packer forever failing to connect via SSH because targetting the wrong previous ip address.
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.
ghost
locked as resolved and limited conversation to collaborators
May 16, 2021
This issue was closed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Overview of the Issue
Packer 1.7.2 fails to connect via SSH during the installation of an Ubuntu 20.04.2 live server because the ip of the guest changes after the first reboot, and the DHCP provides a different ip address. Packer still uses the first seen ip address.
In #8528 , it's claimed that this point is fixed for vmware-iso, but I'm witnessing that with vsphere-iso, the issue remains.
Reproduction Steps
Packer version
1.7.2
Buildfile
sources_ubuntu_20_04.pkr.hcl
Operating system and Environment details
Packer runs on CentOS Linux release 8.3.2011
vSphere is 7.0.2
Log Fragments and crash.log files
2021/04/08 12:09:03 packer-builder-vsphere-iso plugin: VM IP aquired: 10.32.0.142
2021/04/08 12:09:04 packer-builder-vsphere-iso plugin: VM IP is still the same: 10.32.0.142
...
2021/04/08 12:12:30 packer-builder-vsphere-iso plugin: [DEBUG] TCP connection to SSH ip/port failed: dial tcp 10.32.0.142:22: i/o timeout
2021/04/08 12:12:50 packer-builder-vsphere-iso plugin: [DEBUG] TCP connection to SSH ip/port failed: dial tcp 10.32.0.142:22: i/o timeout
2021/04/08 12:12:58 packer-builder-vsphere-iso plugin: [DEBUG] TCP connection to SSH ip/port failed: dial tcp 10.32.0.142:22: connect: no route to host
2021/04/08 12:13:06 packer-builder-vsphere-iso plugin: [DEBUG] TCP connection to SSH ip/port failed: dial tcp 10.32.0.142:22: connect: no route to host
^--- Here, the ip has changed and is not 10.32.0.142 anymore, so Packed won't reach it ever.
Thank you for you help.
Nicolas
The text was updated successfully, but these errors were encountered: