debcrafters-packages team mailing list archive

[Chloé Smith <2112595@xxxxxxxxxxxxxxxxxx>]

** Description changed:

  ==== Bug
  
  The latest release of gce-compute-packages (a.k.a google-compute-engine)
- drops a config file into /etc/systemd/resolved.conf.d that add a
+ 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
  ```

** Description changed:

  ==== Bug
  
  The latest release of gce-compute-packages (a.k.a google-compute-engine)
- drops a config file into /etc/systemd/resolved.conf.d that adds a
- `.local` prefix to the FQDN.
+ 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
  ```

-- 
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:
  New

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