[Bug 2106629] Re: debian/install still installs google_hostname.sh
ChloƩ Smith
2106629 at bugs.launchpad.net
Wed Apr 9 17:59:16 UTC 2025
Confirmed that the proposed changes do indeed fix the issue:
# Created via `gcloud compute instances create current-plucky --image-project ubuntu-os-cloud-devel --image daily-ubuntu-2504-plucky-amd64-v20250409 --metadata-from-file user-data=hostname.yaml`
````
ubuntu at current-plucky:~$ hostname
current-plucky
ubuntu at current-plucky:~$ hostname -f
current-plucky.c.ubuntu-kajiya.internal
ubuntu at current-plucky:~$ dpkg -s google-compute-engine
Package: google-compute-engine
Status: install ok installed
Priority: optional
Section: admin
Installed-Size: 106
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Architecture: all
Source: gce-compute-image-packages
Version: 20250328.00-0ubuntu1
[...]
````
# Created via `gcloud compute instances create plucky-proposed --image-project ubuntu-kajiya --image plucky-proposed --metadata-from-file user-data=hostname.yaml` where the `plucky-proposed` image is identical to `daily-ubuntu-2504-plucky-amd64-v20250409`, but with this proposed package installed instead.
````
ubuntu at cloudinit1:~$ hostname
cloudinit1
ubuntu at cloudinit1:~$ hostname -f
cloudinit2.i9n.cloud-init.io
ubuntu at cloudinit1:~$ dpkg -s google-compute-engine
Package: google-compute-engine
Status: install ok installed
Priority: optional
Section: admin
Installed-Size: 102
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Architecture: all
Source: gce-compute-image-packages
Version: 20250328.00-0ubuntu2
[...]
````
where in both instances, `hostname.yaml` is as follows:
````
#cloud-config
manage_etc_hosts: true
hostname: cloudinit1
fqdn: cloudinit2.i9n.cloud-init.io
create_hostname_file: true
````
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gce-compute-image-packages in
Ubuntu.
https://bugs.launchpad.net/bugs/2106629
Title:
debian/install still installs google_hostname.sh
Status in gce-compute-image-packages package in Ubuntu:
In Progress
Bug description:
In https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-
packages/+bug/2096762 a bad interaction between cloud-init and the
google agents was discovered wrt setting the hostname. That SRU was
halted, and a new version was proposed in
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-
packages/+bug/2106195.
In that latest bug, however, the change was only made to
packaging/ubuntu/install, which is not debian/install and is not used
for building the package. It appears that sometime ago debian/ was a
symlink to packaging/ubuntu, but that's not the case anymore. This
means that the plucky version of gce-compute-image-packages still
installs the troublesome script, and the regression discovered in the
previous SRU is not yet fixed.
ubuntu at p-gce:~$ dpkg -L google-compute-engine | grep google_hostname
/usr/lib/networkd-dispatcher/routable.d/google_hostname.sh
ubuntu at p-gce:~$ apt-cache policy google-compute-engine
google-compute-engine:
Installed: 20250328.00-0ubuntu1
Candidate: 20250328.00-0ubuntu1
Version table:
*** 20250328.00-0ubuntu1 500
500 http://br.archive.ubuntu.com/ubuntu plucky/main amd64 Packages
100 /var/lib/dpkg/status
ubuntu at p-gce:~$
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2106629/+subscriptions
More information about the foundations-bugs
mailing list