[Bug 1713212] Re: changes in >= 234-2ubuntu7 for artful breaks kubuntu CI image build in docker

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 234-2ubuntu10

---------------
systemd (234-2ubuntu10) artful; urgency=medium

  * Do not fail debootstrap if /etc/resolv.conf is immutable. (LP: #1713212)
  * Revert "Create /etc/resolv.conf on resolved start, if it is an empty file."
    As it is ineffective, and correct creation of /etc/resolv.conf has been fixed.
    This reverts commit ccba42504f216f6ffbc54eb2c9af347355f8d86b.
  * initramfs-tools: trigger udevadm add actions with subsystems first.
    This updates the initramfs-tools init-top udev script to trigger udevadm
    actions with type specified. This mimicks the
    systemd-udev-trigger.service. Without type specified only devices are
    triggered, but triggering subsystems may also be required and should happen
    before triggering the devices. This is the case for example on s390x with zdev
    generated udev rules. (LP: #1713536)

 -- Dimitri John Ledkov <xnox at ubuntu.com>  Wed, 30 Aug 2017 11:22:41
+0100

** Changed in: systemd (Ubuntu)
       Status: In Progress => Fix Released

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

Title:
  changes in >= 234-2ubuntu7 for artful breaks kubuntu CI image build in
  docker

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Our live image build in kubuntu CI using docker, now fails since
  changes in 234-2ubuntu7 onwards.

  log: https://kci.pangea.pub/job/iso_artful_stable_amd64/4/console

  14:52:28 ln: cannot remove '/etc/resolv.conf': Device or resource busy
  14:52:28 dpkg: error processing package systemd (--configure):
  14:52:28  subprocess installed post-installation script returned error exit status 1

  234-2ubuntu7 changes:
  https://launchpad.net/ubuntu/+source/systemd/234-2ubuntu7

    * Always setup /etc/resolv.conf on new installations.
      On new installations, /etc/resolv.conf will always exist. Move it to /run
      and replace it with the desired final symlink. (LP: #1712283)
    * Create /etc/resolv.conf on resolved start, if it is an empty file.

  I doubt eventually we will be the only ones to hit the issue.

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