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

[Rik Mills]

Public bug reported:

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.

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New

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

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