-
Notifications
You must be signed in to change notification settings - Fork 51
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
builder googlecompute preserves intermediate machine's hostname instead of set hostname to instance name for newly created machines #103
Comments
Hi @EmilMaksimov apologies for the delay here. Is this still an issue for you? To confirm you are seeing that creating a new image from a Packer built image is reusing the name of the intermediate instance (used to create the image) as the hostname for all newly created images. Is my understanding correct? If so, are the new instances being created manually or via some automated process like Packer or Terraform? If you could provide the template used for creating the initial image that would be helpful. From my understanding hostnames are generated by GCP unless a specific hostname is set at creation time. |
Hi @nywilken , Your understanding is correct. New instances based on newly created packer image are created manually. Template is very simple. Only install SSH and setup user account. Base image is Google'stock image - windows-server-2019-dc-v20220812. Let me know if any other troubleshooting needs to be done.
|
I have the same problem with AlmaLinux 9. In my case it's a configuraiton problem, as provisioning script the config has is very complex. Hostname gets updated to the right one after reboot. |
This issue applies to the
googlecompute
builder.Newly created VM based on a Packer created Windows Image in Google Compute gets hostname set to Packer intermediate machine's hostname (packer-62bd6611-ac4b-9422-203a-ed4b75e1ac50). Every next VM gets hostname set to the same value.
Expected behaviour - Newly create VM get hostname set to instance name
The text was updated successfully, but these errors were encountered: