[Bug 1777900] Re: oem-config breaks the systemd resolved link for /etc/resolv.conf in 18.04 server

[Launchpad Bug Tracker]

This bug was fixed in the package ubiquity - 18.04.14.8

---------------
ubiquity (18.04.14.8) bionic; urgency=medium

  * Revert inclusion of package updates from cosmic.
  * Automatic update of included source packages: console-setup
    1.178ubuntu2.7.

ubiquity (18.04.14.7) bionic; urgency=medium

  [ Dariusz Gadomski ]
  * Implement missing reboot and shutdown methods in debconf_ui (LP: #1749289)

  [ Michael Hudson-Doyle ]
  * Add systemd-resolved to oem-config.target's Wants (LP: #1777900)

 -- Michael Hudson-Doyle <michael.hudson at ubuntu.com>  Sun, 26 Aug 2018
19:53:26 +1200

** Changed in: ubiquity (Ubuntu Bionic)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1777900

Title:
  oem-config breaks the systemd resolved link for /etc/resolv.conf in
  18.04 server

Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubiquity source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  When ubuntu 18.04 server is trying to do an OEM installation using oem-config-firstboot, the  ubiquity breaks the symlink /etc/resolv.conf -> /run/systemd/resolv/stub-resolv.conf, replacing /etc/resolv.conf with a 0-byte file and thereby breaking name resolution.

  [Test Case]
  The reproducer steps:
  1. Prepare ubuntu-server with d-i version
  2. Install iso
  3. apt install oem-config ubiquity-frontend-debconf oem-config-debconf
  5. oem-config-prepare -q
  6. reboot
  7. enter oem-config and finish it
  8. check if /etc/resolv.conf is broken (actually it becomes a zero-byte file)

  [Regression potential]
  The fix is simple, merely adding a service to oem-config.target's Wants=. Even if the service somehow fails to start or is not present on a system, the other functionality of oem-config will be unaffected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1777900/+subscriptions