← Back to team overview

touch-packages team mailing list archive

[Bug 1431107] Re: ordering cycles with lvm2 init script with inappropriate rc2.d links

 

This bug was fixed in the package systemd - 219-6ubuntu1

---------------
systemd (219-6ubuntu1) vivid; urgency=medium

  * Merge with Debian experimental branch. Remaining Ubuntu changes:
    - Hack to support system-image read-only /etc, and modify files in
      /etc/writable/ instead.
    - Keep our much simpler udev maintainer scripts (all platforms must
      support udev, no debconf).
    - initramfs init-top: Drop $ROOTDELAY, we do that in a more sensible way
      with wait-for-root. Will get applicable to Debian once Debian gets
      wait-for-root in initramfs-tools.
    - initramfs init-bottom: If LVM is installed, settle udev,
      otherwise we get missing LV symlinks. Workaround for LP #1185394.
    - Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv
      dependencies to "lvm2" which is handled with udev rules in Ubuntu.
    - Provide shutdown fallback for upstart. (LP: #1370329)
    - debian/extra/ifup@.service: Additionally run for "auto" class. We don't
      really support "allow-hotplug" in Ubuntu at the moment, so we need to
      deal with "auto" devices appearing after "/etc/init.d/networking start"
      already ran. (LP: #1374521) Also, check if devices are actually defined
      in /etc/network/interfaces as we don't use Debian's net.agent.
    - ifup@.service: Drop dependency on networking.service (i. e.
      /etc/init.d/networking), and merely ensure that /run/network exists.
      This avoids unnecessary dependencies/waiting during boot and dependency
      cycles if hooks wait for other interfaces to come up (like ifenslave
      with bonding interfaces). (LP: #1414544)
    - Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In
      Ubuntu we currently keep the setting whether the RTC is in local or UTC
      time in /etc/default/rcS "UTC=yes|no", instead of /etc/adjtime.
      (LP: #1377258)
    - Put session scopes into all cgroup controllers. This makes unprivileged
      user LXC containers work under systemd. (LP: #1346734)
    - 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)
    - Lower Breaks: to plymouth version which has the udev inotify fix in
      Ubuntu.
    - Lower libappamor1 dep to the Ubuntu version where it moved to /lib.
    - Change systemd-sysv's conflicts to upstart-sysv. (LP: #1422681)
    - Make failure of boot-and-services NSpawn.test_boot non-fatal for now.
      This currently fails when being triggered by Jenkins, but is totally
      unreproducible when running this manually on the exact same machine.

    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.

  * Add debian/udev.lvm2.service to avoid running the dummy lvm2 init script.
    (LP: #1431107)

systemd (219-6) experimental; urgency=medium

  [ Martin Pitt ]
  * Import patches from v219-stable branch (up to 85a6fab).
  * boot-and-services autopkgtest: Add missing python3 test dependency.
  * Make apparmor run before networking, to ensure that profiles apply to
    e. g. dhclient (LP: #1438249):
    - Rename networking.service.d/network-pre.conf to systemd.conf, and add
      After=apparmor.service.
    - ifup@.service: Add After=apparmor.service.
  * udev: Drop hwdb-update dependency, which got introduced by the above
    v219-stable branch. This causes udev and plymouth to start too late and
    isn't really needed in Debian yet as we don't support stateless systems
    yet and handle hwdb.bin updates through dpkg triggers. (LP: #1439301)

  [ Didier Roche ]
  * Fix mount point detection on overlayfs and similar file systems without
    name_to_handle_at() and st_dev support. (LP: #1411140)

  [ Christian Seiler ]
  * Make the journald to syslog forwarding more robust by increasing the
    maximum datagram queue length from 10 to 512. (Closes: #762700)

  [ Marco d'Itri ]
  * Avoid writing duplicate entries in 70-persistent-net.rules by double
    checking if the new udev rule has already been written for the given
    interface. This happens if multiple add events are generated before the
    write_net_rules script returns and udevd renames the interface.
    (Closes: #765577)
 -- Martin Pitt <martin.pitt@xxxxxxxxxx>   Thu, 02 Apr 2015 10:08:44 +0200

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1431107

Title:
  ordering cycles with lvm2 init script with inappropriate rc2.d links

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  After switching to systemd, the AppArmor service often fails to start
  on boot.  This seems to happen at least 50% of the times I turn on the
  system.  If I attempt to start the process again after the system is
  otherwise finished booting, it works fine.  I also have another system
  with the same software configuration but a much slower storage system
  (HDD instead of SSD) which never suffers from this problem, so I think
  it is probably a race condition.  If I do "systemctl status apparmor",
  I get the following output:

  michael@mamarley-laptop:~$ sudo systemctl status apparmor
  ● apparmor.service - LSB: AppArmor initialization
     Loaded: loaded (/etc/init.d/apparmor)
     Active: failed (Result: exit-code) since Wed 2015-03-11 21:25:44 EDT; 1min 5s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 237 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)

  Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
  Mar 11 21:25:44 mamarley-laptop apparmor[237]: mkstemp: Read-only file system
  Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
  Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service: control process exited, code=exited status=123
  Mar 11 21:25:44 mamarley-laptop apparmor[237]: ...fail!
  Mar 11 21:25:44 mamarley-laptop systemd[1]: Failed to start LSB: AppArmor initialization.
  Mar 11 21:25:44 mamarley-laptop systemd[1]: Unit apparmor.service entered failed state.
  Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1
  Uname: Linux 3.19.0-9-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 11 21:30:08 2015
  InstallationDate: Installed on 2014-06-01 (283 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1)
  MachineType: LENOVO 2359CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-lowlatency root=UUID=1f7829ef-ffb8-4182-ac92-40d613ea78c9 ro elevator=deadline intel_pstate=enable "acpi_osi=Windows 2012"
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/21/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G4ETA2WW (2.62 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2359CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: dmi:bvnLENOVO:bvrG4ETA2WW(2.62):bd08/21/2014:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2359CTO
  dmi.product.version: ThinkPad T530
  dmi.sys.vendor: LENOVO

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


References