debcrafters-packages team mailing list archive

[Launchpad Bug Tracker <2112595@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package gce-compute-image-packages -
20250501.00-0ubuntu1

---------------
gce-compute-image-packages (20250501.00-0ubuntu1) questing; urgency=medium

  * New upstream version for upstream tag 20250501.00. (LP: #2113788)
    * This version fixes LP: #2112595 (`Domains=local` is appending
      `.local` to the FQDN) as well.

 -- Chloé 'kajiya' Smith <chloe.smith@xxxxxxxxxxxxx>  Mon, 09 Jun 2025
20:58:04 +0100

** Changed in: gce-compute-image-packages (Ubuntu)
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to gce-compute-image-packages
in Ubuntu.
https://bugs.launchpad.net/bugs/2112595

Title:
  `Domains=local` is appending `.local` to the FQDN

Status in gce-compute-image-packages package in Ubuntu:
  Fix Released

Bug description:
  ==== Bug

  The latest release of gce-compute-packages (a.k.a google-compute-
  engine) 20250328.00-0ubuntu2 drops a config file into
  /etc/systemd/resolved.conf.d that adds a `.local` prefix to the FQDN.

  ````
  ubuntu@jammy-lp:~$ hostname -f
  jammy-lp.local
  ````

  [Impact]

  This will likely affect users with scripts calling `hostname` or those
  who rely on a known FQDN

  [Mitigation]

  Editing the `gce-resolved.conf` file to use `Domains=~local` suffices.
  A one line fix to use is:

  ```
  sudo sed --in-place 's,Domains=local,Domains=~local,g' /etc/systemd/resolved.conf.d/gce-resolved.conf
  ```

  followed by restarting the `systemd-resolved.service`:

  ```
  sudo systemctl restart systemd-resolved.service
  ```

  fixes the issue:

  ```
  ubuntu@jammy-lp:~$ hostname -f
  jammy-lp.c.ubuntu-kajiya.internal
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2112595/+subscriptions