Copying catred's comment here for completeness [0] > This SRU creates a regression in cloud-init behaviour.
Using the following user_data hostname.yaml: #cloud-config manage_etc_hosts: true hostname: cloudinit1 fqdn: cloudinit2.i9n.cloud-init.io create_hostname_file: true On an existing noble image: $ gcloud compute instances create hostname-noble --image-project ubuntu-os-cloud --image ubuntu-2404- noble-amd64-v20250313 --metadata-from-file user-data=hostname.yaml [...] catred@cloudinit1:~$ hostname cloudinit1 catred@cloudinit1:~$ hostname -f cloudinit2.i9n.cloud-init.io With the proposed package changes: $ gcloud compute instances create hostname-noble-sru --image-project ubuntu-os-cloud-image-proposed -- image testing-ubuntu-guest-2404-noble-amd64-v20250218 --metadata-from-file user-data=hostname.yaml [...] catred@hostname-noble-sru:~$ hostname hostname-noble-sru catred@hostname-noble-sru:~$ hostname -f hostname-noble-sru.c.ubuntu-catred.internal A user attempting to set their hostname via cloud-init will no longer get their expected behaviour, but will get the hostname set as the internal default Google hostname. For any user using cloud-init to manage a large fleet of servers this could be a breaking change. [0]: https://bugs.launchpad.net/ubuntu/+source/google-guest- agent/+bug/2096765/comments/19 ** Tags removed: patch verification-needed verification-needed-focal verification-needed-jammy verification-needed-noble verification-needed-oracular ** Tags added: regression-proposed verification-failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2096762 Title: Please update to 20250107.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2096762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
