[Bug 1545707] Re: Error message "Operation failed: No such file or directory" on installing/reconfiguring systemd

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 229-2ubuntu1

---------------
systemd (229-2ubuntu1) xenial; urgency=medium

  * Merge with Debian unstable. Remaining Ubuntu changes:
    - Hack to support system-image read-only /etc, and modify files in
      /etc/writable/ instead.

    Upgrade fixes, keep until 16.04 LTS release:
    - systemd Conflicts/Replaces/Provides systemd-services.
    - Remove obsolete systemd-logind upstart job.
    - Clean up obsolete /etc/udev/rules.d/README.
    - systemd.postinst: Migrate mountall specific fstab options to standard
      util-linux "nofail" option.
    - systemctl: Don't forward telinit u to upstart. This works around
      upstart's Restart() always reexec'ing /sbin/init on Restart(), even if
      that changes to point to systemd during the upgrade. This avoids running
      systemd during a dist-upgrade. (LP: #1430479)
    - Provide shutdown fallback for upstart. (LP: #1370329)
    - Break lvm (<< 2.02.133-1ubuntu1) and remove our dummy /etc/init.d/lvm2
      on upgrades, as it's shipped by lvm2 now.
    - Make udev break on mdadm << 3.3-2ubuntu3, as udev's init script dropped
      the "Provides: raid-mdadm".
    - Clean up /var/log/udev on upgrade (which is written under upstart, but
      not under systemd). (LP: #1537211)
    - Migrate existing s390x network configuration to new names. (LP: #1526808)
    - systemd.postinst: Bump Version comparison for migrating the UTC setting
      from /etc/default/rcS to /etc/adjtime, to run it for upgrades to 16.04.

systemd (229-2) unstable; urgency=medium

  * time-util: map ALARM clockids to non-ALARM clockids in now(), to work on
    architectures which don't support CLOCK_BOOTTIME_ALARM. Fixes FTBFS on
    many architectures.
  * debian/systemd.postinst: Add missing newline to /etc/adjtime migration.
    (See #699554)
  * debian/systemd.postinst: Only try to enable tmp.mount if we actually
    copied it to /etc. Don't try to enable a generated unit. (LP: #1545707)
  * debian/tests/boot-and-services: Increase timeouts of test_bash_crash from
    5 to 10 seconds, and sync the journal after every iteration.
  * debian/extra/checkout-upstream: Try again after one minute if git checkout
    fails, to avoid failures from transient network errors.
  * debian/tests/systemd-fsckd: Use grub.d/50-cloudimg-settings.cfg as a
    template for generating our custom one instead of 90-autopkgtest.cfg. The
    latter does not exist on non-x86 architectures and is not relevant for
    this test.
  * debian/tests/boot-and-services: Skip journal test for test_bash_crash when
    running against upstream, as this currently fails most of the time. To be
    investigated.
  * debian/tests/networkd: Skip test_coldplug_dhcp_ip6 when running against
    upstream, as this is brittle there. To be investigated.
  * debian/tests/bootchart: Skip test if bootchart is not available or
    testing in upstream mode. bootchart got removed from master and will be
    moved to a separate repository.
  * debian/tests/boot-and-services: Show verbose journal output on failure in
    nspawn test, and sync journal before.
  * Move systemd-coredump socket and service into systemd-coredump binary
    package.
  * Revert changing the default core dump ulimit and core_pattern. This
    completely breaks core dumps without systemd-coredump. It's also
    contradicting core(8). (Closes: #815020)
  * Fix addresses for type "sit" tunnels. (Closes: #816132)
  * networkd: Go back to letting the kernel handle IPv6 router advertisements,
    as networkd's own currently has too many regressions. Thanks to Stefan
    Lippers-Hollmann for investigating this! (Closes: #814566,
    #814667, #815586, #815884, #815793)

 -- Martin Pitt <martin.pitt at ubuntu.com>  Sun, 28 Feb 2016 22:58:06
+0100

** Changed in: systemd (Ubuntu)
       Status: Fix Committed => 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/1545707

Title:
  Error message "Operation failed: No such file or directory" on
  installing/reconfiguring systemd

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  I'm using Ubuntu 16.04 dev with systemd 229-1ubuntu2 and on
  installing/reconfiguring it I'm getting this output (the first error
  has already its own bug report here:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1475094 ):

  root at ubuntu:~# dpkg-reconfigure systemd
  addgroup: The group `systemd-journal' already exists as a system group. Exiting.
  Operation failed: No such file or directory

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