-
Notifications
You must be signed in to change notification settings - Fork 928
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
cc-set-hostname (hostname and fqdn) are not working on google cloud VMs Ubuntu 24.04 #6058
Comments
On Noble and above on GCE, setting the hostname also requires |
No, I tried with and without, and it doesn't set the hostname or fqdn either way |
@rajannpatel , whoops, looks like your header is wrong. |
That's embarassing. I guess it's working as intended, for posterity I'm including some outputs from tests which appear to be working. I don't understand why I'm seeing some akamai domains in the output, but perhaps that is a byproduct of me using "example.com" If this looks right to you, we can close this ticket.
|
Bug report
The steps here do not seem to impact the hostname on google cloud VMs:
https://cloudinit.readthedocs.io/en/latest/reference/modules.html#mod-cc-set-hostname
Steps to reproduce the problem
This cloud-init.yaml file, when used to launch a virtual machine on Google Cloud, does not make any changes to the hostname.
This is tested with the
hostname
command, once the machine boots up.Environment details
The text was updated successfully, but these errors were encountered: