touch-packages team mailing list archive

[Dylan Borg <borgdylan@xxxxxxxxxxx>]

Public bug reported:

Currently the failsafe boot service is only shipped as an upstart job.
Since in utopic there is an ongoing transition to systemd there is a
race between upstart and systemd when it comes to networking. Network
manager may be getting started by systemd (package has a systemd unit
inside) which is not allowing events required by failsafe boot to arrive
to it so that it aborts the extra 2 minutes hang as it is running on
upstart (and cannot run on systemd).

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

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

Title:
  upstart package should also include a systemd unit for failsafe boot

Status in “upstart” package in Ubuntu:
  New

Bug description:
  Currently the failsafe boot service is only shipped as an upstart job.
  Since in utopic there is an ongoing transition to systemd there is a
  race between upstart and systemd when it comes to networking. Network
  manager may be getting started by systemd (package has a systemd unit
  inside) which is not allowing events required by failsafe boot to
  arrive to it so that it aborts the extra 2 minutes hang as it is
  running on upstart (and cannot run on systemd).

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