touch-packages team mailing list archive

[Steve Langasek <steve.langasek@xxxxxxxxxxxxx>]

Sorry, that part of the systemd.special(7) manpage doesn't actually
explain the problem with network.target.  The problem is described here:

SPECIAL PASSIVE SYSTEM UNITS
       A number of special system targets are defined that can be used to
       properly order boot-up of optional services. These targets are
       generally not part of the initial boot transaction, unless they are
       explicitly pulled in by one of the implementing services. Note
       specifically that these passive target units are generally not pulled
       in by the consumer of a service, but by the provider of the service.
       This means: a consuming service should order itself after these targets
       (as appropriate), but not pull it in. A providing service should order
       itself before these targets (as appropriate) and pull it in (via a
       Wants= type dependency).

network.target is one of these "special passive system units".

Locally fixing these bugs in cloud-init and ifupdown does not unblock
the networkless boot.

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

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