← Back to team overview

touch-packages team mailing list archive

[Bug 1431836] Re: Boot process takes too long when Ethernet is not connected

 

Ah, this is snappy, this explains all the errors about read-only
directories.

In the "with ethernet" case, boot started at 19:00:44, and eth0 DHCP is
done at 19:00:57, so 13 s. Then it spends half a minute or so in cloud-
init and click hooks, so that's not systemd's fault. So I consider the
"with ethernet" case okay (feel free to report bugs against ubuntu-
snappy against wasting all that time in cloud-init, though -- I don't
think it ought to take that long except for the first boot).

In the "no ethernet" case, boot started at 19:00:44 too. That's really
curious -- it's not the same file, so not just an attachment accident.
Is there a problem with your clock or so? At 19:00:49 eth0 starts up,
and then there are loots of repeated failed attempts to up it. At
19:01:15 (+31 s) cloud-init starts, at 19:02:53 (+2:09) eth0 gives up.
Apparently at 19:06:02 you plugged in the ethernet cable? It seems to
connect then, and reaches the "network" target. That's indeed buggy,
network.target should be reached way earlier, the missing eth link
should only block "networking.target".

So there are two issues here:

  - At the moment, snappy (or at least your image) is assuming ethernet
connectivity, as you obviously have eth0 in /etc/network/interfaces.d/
somewhere (pending confirmation, see my previous question). In the
future we probably want to make this more dynamic, using  networkd or
NetworkManager or something such.

 - Something there is blocking network.target on getting eth0 up, which
is wrong. Can you please give me the output of "systemctl list-
dependencies network.target"?

** Also affects: snappy-ubuntu
   Importance: Undecided
       Status: New

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

Title:
  Boot process takes too long when Ethernet is not connected

Status in Snappy Ubuntu:
  New
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  The boot process takes a minute with Internet access (e.g.: Ethernet)
  and several minutes when no Ethernet is connected. The kernel dump for
  the later is shown at
  https://gist.github.com/vmayoral/135aef30218b8d00d4f1.

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


References