touch-packages team mailing list archive

[Steve Langasek <steve.langasek@xxxxxxxxxxxxx>]

The remaining issue is that /etc/init.d/networking is sequenced before
network.target, with no timeout.

# cat /run/systemd/generator/networking.service.d/50-insserv.conf-\$network.conf 
# Automatically generated by systemd-insserv-generator

[Unit]
Wants=network.target
Before=network.target
#

ifupdown has a systemd hook that's intended to reproduce the "network-
failsafe" behavior that we had under upstart; but this only hooks into
the network-online target, not the earlier network target which is the
one that actually blocks boot (nothing on a snappy system actually
references network-online.target).

We should definitely not be blocking network.target indefinitely on boot
waiting for the results of /etc/init.d/networking.  There needs to be
some kind of timeout to allow the system to continue booting when a
network device configured in /etc/network can't be brought online -
while also allowing the system to continue trying to bring that network
device up in the background.

Since
/run/systemd/generator/networking.service.d/50-insserv.conf-\$network.conf
is created by systemd-insserv-generator, opening a systemd task as well.

** Also affects: systemd (Ubuntu)
   Importance: Undecided
       Status: New

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

Title:
  Ubuntu Core provides no console login prompt if network is unavailable

Status in Snappy Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  New
Status in ifupdown package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu Core provides no console login prompt if network is
  unavailable.

  If I plug ethernet in, it boots to the login prompt fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy-ubuntu/+bug/1425376/+subscriptions