> network-online.target shouldn't be completing until all 'auto'
interfaces have link or some timeout is hit.
That already is the case -- networking.service (which is ifupdown, aka
"Started Raise network interfaces") is Before=network-online.target, and
the log proves that this works.
You only pasted a small log excerpt, where e. g. dhclient and ifupdown
messages aren't visible. But ifupdown clearly thinks that your
enp2s0/eno1 links *are* up, assuming that you actually configure them in
/etc/network/interfaces or interfaces.d/*. What are the corresponding
entries there? If they are "auto", then networking.service ought to
wait. If they are "allow-hotplug", they they won't wait. You wrote
"auto" above, but let's make sure.
** Summary changed:
- network dependent services starting before network is up
+ networking.service does not wait for interfaces to be up
** Package changed: openvpn (Ubuntu) => ifupdown (Ubuntu)
** Changed in: ifupdown (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1588915
Title:
networking.service does not wait for interfaces to be up
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1588915/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
