[Touch-packages] [Bug 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged
https://github.com/systemd/systemd/issues/8686 seems related. ** Bug watch added: github.com/systemd/systemd/issues #8686 https://github.com/systemd/systemd/issues/8686 -- 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/1728181 Title: systemd-networkd-wait-online waits when devices are unmanaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: I started a system with cloud-init disabled, etc. and a single real network interface (ens3) that could be configured. That VM has no configuration whatsoever for systemd-networkd, as that would have to have been written by netplan, and cloud-init did not generate netplan config (because it was disabled). So: root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route d-networkd-wait-online --ignore=lo ignoring: lo Event loop failed: Connection timed out root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 ens3 ether off unmanaged 3 sit0 sitoff unmanaged 3 links listed. root@ubuntu:/etc/systemd/system/network-online.target.wants# The system took 120 seconds to complete boot, because wait-online had to finish; and running wait-online from the system afterwards also waits 120 seconds (its default timeout). If there is no configuration for an interface, it's unmanaged (as shown by networkctl), so wait-online should not wait, and simply report that all interfaces are unmanaged, possibly returning an error so we don't reach network-online. FWIW, having wait-online look up configuration might later be useful also to figure out if an interface was configured, but marked as optional (such that it is explicitly not required to be up at boot), or if we want to configure network devices but specify that networkd should *not* bring them online (like "administratively disabled" interfaces in Cisco world using the "shutdown" command). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged
I face the same issue > # dpkg -l systemd > ... > ||/ Name VersionArchitectureDescription > +++-==-==-===-== > ii systemd237-3ubuntu10.3amd64 system and service manager > # networkctl > IDX LINK TYPE OPERATIONAL SETUP > 1 lo loopback carrier unmanaged > 2 ens3 ether routableconfiguring > 3 ens4 ether routableunmanaged > Aug 03 14:00:53 test-vm systemd-networkd-wait-online[4273]: Event loop failed: Connection timed out -- 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/1728181 Title: systemd-networkd-wait-online waits when devices are unmanaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: I started a system with cloud-init disabled, etc. and a single real network interface (ens3) that could be configured. That VM has no configuration whatsoever for systemd-networkd, as that would have to have been written by netplan, and cloud-init did not generate netplan config (because it was disabled). So: root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route d-networkd-wait-online --ignore=lo ignoring: lo Event loop failed: Connection timed out root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 ens3 ether off unmanaged 3 sit0 sitoff unmanaged 3 links listed. root@ubuntu:/etc/systemd/system/network-online.target.wants# The system took 120 seconds to complete boot, because wait-online had to finish; and running wait-online from the system afterwards also waits 120 seconds (its default timeout). If there is no configuration for an interface, it's unmanaged (as shown by networkctl), so wait-online should not wait, and simply report that all interfaces are unmanaged, possibly returning an error so we don't reach network-online. FWIW, having wait-online look up configuration might later be useful also to figure out if an interface was configured, but marked as optional (such that it is explicitly not required to be up at boot), or if we want to configure network devices but specify that networkd should *not* bring them online (like "administratively disabled" interfaces in Cisco world using the "shutdown" command). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged
@dino99 Please specify version of systemd installed, e.g. $ dpkg -l systemd Please attach the output of $ networkctl -- 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/1728181 Title: systemd-networkd-wait-online waits when devices are unmanaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: I started a system with cloud-init disabled, etc. and a single real network interface (ens3) that could be configured. That VM has no configuration whatsoever for systemd-networkd, as that would have to have been written by netplan, and cloud-init did not generate netplan config (because it was disabled). So: root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route d-networkd-wait-online --ignore=lo ignoring: lo Event loop failed: Connection timed out root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 ens3 ether off unmanaged 3 sit0 sitoff unmanaged 3 links listed. root@ubuntu:/etc/systemd/system/network-online.target.wants# The system took 120 seconds to complete boot, because wait-online had to finish; and running wait-online from the system afterwards also waits 120 seconds (its default timeout). If there is no configuration for an interface, it's unmanaged (as shown by networkctl), so wait-online should not wait, and simply report that all interfaces are unmanaged, possibly returning an error so we don't reach network-online. FWIW, having wait-online look up configuration might later be useful also to figure out if an interface was configured, but marked as optional (such that it is explicitly not required to be up at boot), or if we want to configure network devices but specify that networkd should *not* bring them online (like "administratively disabled" interfaces in Cisco world using the "shutdown" command). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged
This is still not fixed on bionic dbus-daemon[1299]: [session uid=1000 pid=1299] Activating service name='org.gnome.Identity' requested by ':1.39' (uid=1000 pid=1524 comm="/usr/lib/gnome-online-accounts/goa-daemon " label="unconfined") systemd-networkd-wait-online[771]: Event loop failed: Connection timed out systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'. -- 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/1728181 Title: systemd-networkd-wait-online waits when devices are unmanaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: I started a system with cloud-init disabled, etc. and a single real network interface (ens3) that could be configured. That VM has no configuration whatsoever for systemd-networkd, as that would have to have been written by netplan, and cloud-init did not generate netplan config (because it was disabled). So: root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route d-networkd-wait-online --ignore=lo ignoring: lo Event loop failed: Connection timed out root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 ens3 ether off unmanaged 3 sit0 sitoff unmanaged 3 links listed. root@ubuntu:/etc/systemd/system/network-online.target.wants# The system took 120 seconds to complete boot, because wait-online had to finish; and running wait-online from the system afterwards also waits 120 seconds (its default timeout). If there is no configuration for an interface, it's unmanaged (as shown by networkctl), so wait-online should not wait, and simply report that all interfaces are unmanaged, possibly returning an error so we don't reach network-online. FWIW, having wait-online look up configuration might later be useful also to figure out if an interface was configured, but marked as optional (such that it is explicitly not required to be up at boot), or if we want to configure network devices but specify that networkd should *not* bring them online (like "administratively disabled" interfaces in Cisco world using the "shutdown" command). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged
This bug was fixed in the package systemd - 237-3ubuntu6 --- systemd (237-3ubuntu6) bionic; urgency=medium * Adjust the new dropin test, for v237 systemd. * Refresh the keyring patch, to the one merged. -- Dimitri John Ledkov Tue, 27 Mar 2018 13:40:09 +0100 ** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1728181 Title: systemd-networkd-wait-online waits when devices are unmanaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: I started a system with cloud-init disabled, etc. and a single real network interface (ens3) that could be configured. That VM has no configuration whatsoever for systemd-networkd, as that would have to have been written by netplan, and cloud-init did not generate netplan config (because it was disabled). So: root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route d-networkd-wait-online --ignore=lo ignoring: lo Event loop failed: Connection timed out root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 ens3 ether off unmanaged 3 sit0 sitoff unmanaged 3 links listed. root@ubuntu:/etc/systemd/system/network-online.target.wants# The system took 120 seconds to complete boot, because wait-online had to finish; and running wait-online from the system afterwards also waits 120 seconds (its default timeout). If there is no configuration for an interface, it's unmanaged (as shown by networkctl), so wait-online should not wait, and simply report that all interfaces are unmanaged, possibly returning an error so we don't reach network-online. FWIW, having wait-online look up configuration might later be useful also to figure out if an interface was configured, but marked as optional (such that it is explicitly not required to be up at boot), or if we want to configure network devices but specify that networkd should *not* bring them online (like "administratively disabled" interfaces in Cisco world using the "shutdown" command). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged
** Tags added: id-5ab94d247a8174c33895ec21 -- 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/1728181 Title: systemd-networkd-wait-online waits when devices are unmanaged Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: Fix Committed Bug description: I started a system with cloud-init disabled, etc. and a single real network interface (ens3) that could be configured. That VM has no configuration whatsoever for systemd-networkd, as that would have to have been written by netplan, and cloud-init did not generate netplan config (because it was disabled). So: root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route d-networkd-wait-online --ignore=lo ignoring: lo Event loop failed: Connection timed out root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 ens3 ether off unmanaged 3 sit0 sitoff unmanaged 3 links listed. root@ubuntu:/etc/systemd/system/network-online.target.wants# The system took 120 seconds to complete boot, because wait-online had to finish; and running wait-online from the system afterwards also waits 120 seconds (its default timeout). If there is no configuration for an interface, it's unmanaged (as shown by networkctl), so wait-online should not wait, and simply report that all interfaces are unmanaged, possibly returning an error so we don't reach network-online. FWIW, having wait-online look up configuration might later be useful also to figure out if an interface was configured, but marked as optional (such that it is explicitly not required to be up at boot), or if we want to configure network devices but specify that networkd should *not* bring them online (like "administratively disabled" interfaces in Cisco world using the "shutdown" command). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged
** Changed in: systemd (Ubuntu Bionic) Status: Confirmed => Fix Committed -- 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/1728181 Title: systemd-networkd-wait-online waits when devices are unmanaged Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: Fix Committed Bug description: I started a system with cloud-init disabled, etc. and a single real network interface (ens3) that could be configured. That VM has no configuration whatsoever for systemd-networkd, as that would have to have been written by netplan, and cloud-init did not generate netplan config (because it was disabled). So: root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route d-networkd-wait-online --ignore=lo ignoring: lo Event loop failed: Connection timed out root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 ens3 ether off unmanaged 3 sit0 sitoff unmanaged 3 links listed. root@ubuntu:/etc/systemd/system/network-online.target.wants# The system took 120 seconds to complete boot, because wait-online had to finish; and running wait-online from the system afterwards also waits 120 seconds (its default timeout). If there is no configuration for an interface, it's unmanaged (as shown by networkctl), so wait-online should not wait, and simply report that all interfaces are unmanaged, possibly returning an error so we don't reach network-online. FWIW, having wait-online look up configuration might later be useful also to figure out if an interface was configured, but marked as optional (such that it is explicitly not required to be up at boot), or if we want to configure network devices but specify that networkd should *not* bring them online (like "administratively disabled" interfaces in Cisco world using the "shutdown" command). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged
** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: Confirmed ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: systemd (Ubuntu Bionic) Milestone: None => ubuntu-18.03 -- 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/1728181 Title: systemd-networkd-wait-online waits when devices are unmanaged Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Bionic: Confirmed Bug description: I started a system with cloud-init disabled, etc. and a single real network interface (ens3) that could be configured. That VM has no configuration whatsoever for systemd-networkd, as that would have to have been written by netplan, and cloud-init did not generate netplan config (because it was disabled). So: root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route d-networkd-wait-online --ignore=lo ignoring: lo Event loop failed: Connection timed out root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 ens3 ether off unmanaged 3 sit0 sitoff unmanaged 3 links listed. root@ubuntu:/etc/systemd/system/network-online.target.wants# The system took 120 seconds to complete boot, because wait-online had to finish; and running wait-online from the system afterwards also waits 120 seconds (its default timeout). If there is no configuration for an interface, it's unmanaged (as shown by networkctl), so wait-online should not wait, and simply report that all interfaces are unmanaged, possibly returning an error so we don't reach network-online. FWIW, having wait-online look up configuration might later be useful also to figure out if an interface was configured, but marked as optional (such that it is explicitly not required to be up at boot), or if we want to configure network devices but specify that networkd should *not* bring them online (like "administratively disabled" interfaces in Cisco world using the "shutdown" command). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged
An other case: get the same issue via a netboot install ( lp:1736880 ) I get a 'Wired unmanaged" into dropdown menu -- 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/1728181 Title: systemd-networkd-wait-online waits when devices are unmanaged Status in systemd package in Ubuntu: Confirmed Bug description: I started a system with cloud-init disabled, etc. and a single real network interface (ens3) that could be configured. That VM has no configuration whatsoever for systemd-networkd, as that would have to have been written by netplan, and cloud-init did not generate netplan config (because it was disabled). So: root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route d-networkd-wait-online --ignore=lo ignoring: lo Event loop failed: Connection timed out root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 ens3 ether off unmanaged 3 sit0 sitoff unmanaged 3 links listed. root@ubuntu:/etc/systemd/system/network-online.target.wants# The system took 120 seconds to complete boot, because wait-online had to finish; and running wait-online from the system afterwards also waits 120 seconds (its default timeout). If there is no configuration for an interface, it's unmanaged (as shown by networkctl), so wait-online should not wait, and simply report that all interfaces are unmanaged, possibly returning an error so we don't reach network-online. FWIW, having wait-online look up configuration might later be useful also to figure out if an interface was configured, but marked as optional (such that it is explicitly not required to be up at boot), or if we want to configure network devices but specify that networkd should *not* bring them online (like "administratively disabled" interfaces in Cisco world using the "shutdown" command). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged
This bug may be a duplicate of LP #1717152 -- 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/1728181 Title: systemd-networkd-wait-online waits when devices are unmanaged Status in systemd package in Ubuntu: Confirmed Bug description: I started a system with cloud-init disabled, etc. and a single real network interface (ens3) that could be configured. That VM has no configuration whatsoever for systemd-networkd, as that would have to have been written by netplan, and cloud-init did not generate netplan config (because it was disabled). So: root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route d-networkd-wait-online --ignore=lo ignoring: lo Event loop failed: Connection timed out root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 ens3 ether off unmanaged 3 sit0 sitoff unmanaged 3 links listed. root@ubuntu:/etc/systemd/system/network-online.target.wants# The system took 120 seconds to complete boot, because wait-online had to finish; and running wait-online from the system afterwards also waits 120 seconds (its default timeout). If there is no configuration for an interface, it's unmanaged (as shown by networkctl), so wait-online should not wait, and simply report that all interfaces are unmanaged, possibly returning an error so we don't reach network-online. FWIW, having wait-online look up configuration might later be useful also to figure out if an interface was configured, but marked as optional (such that it is explicitly not required to be up at boot), or if we want to configure network devices but specify that networkd should *not* bring them online (like "administratively disabled" interfaces in Cisco world using the "shutdown" command). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged
I'm not using cloud-init. My network devices are not managed because I disabled NetworkManager.service shortly after installing 17.10 on bare metal Nov 5, 2017 9:44 AM EDT. I think there were too many fires then and I didn't want to try to convince NetworkManager to use a bridge. I just lived with the two minute delay while working on the four minute delay LP 1731566 and the "BUG: unable to handle kernel NULL pointer dereference at (null)" LP 1730374 until work on that last issue lead to the two minute delay clearing up as a side-effect. -- 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/1728181 Title: systemd-networkd-wait-online waits when devices are unmanaged Status in systemd package in Ubuntu: Confirmed Bug description: I started a system with cloud-init disabled, etc. and a single real network interface (ens3) that could be configured. That VM has no configuration whatsoever for systemd-networkd, as that would have to have been written by netplan, and cloud-init did not generate netplan config (because it was disabled). So: root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route d-networkd-wait-online --ignore=lo ignoring: lo Event loop failed: Connection timed out root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 ens3 ether off unmanaged 3 sit0 sitoff unmanaged 3 links listed. root@ubuntu:/etc/systemd/system/network-online.target.wants# The system took 120 seconds to complete boot, because wait-online had to finish; and running wait-online from the system afterwards also waits 120 seconds (its default timeout). If there is no configuration for an interface, it's unmanaged (as shown by networkctl), so wait-online should not wait, and simply report that all interfaces are unmanaged, possibly returning an error so we don't reach network-online. FWIW, having wait-online look up configuration might later be useful also to figure out if an interface was configured, but marked as optional (such that it is explicitly not required to be up at boot), or if we want to configure network devices but specify that networkd should *not* bring them online (like "administratively disabled" interfaces in Cisco world using the "shutdown" command). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged
This morning I found out that if I boot linux-image-4.13.0-17-generic I get a hang at Nov 23 07:12:47 lakshmi NetworkManager[1795]: [1511439167.0455] manager: rfkill: WWAN hardware radio set enabled Nov 23 07:14:30 lakshmi systemd-networkd-wait-online[1454]: Event loop failed: Connection timed out But if I boot linux-image-4.14.2-041402-generic there is no two minute delay. -- 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/1728181 Title: systemd-networkd-wait-online waits when devices are unmanaged Status in systemd package in Ubuntu: Confirmed Bug description: I started a system with cloud-init disabled, etc. and a single real network interface (ens3) that could be configured. That VM has no configuration whatsoever for systemd-networkd, as that would have to have been written by netplan, and cloud-init did not generate netplan config (because it was disabled). So: root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route d-networkd-wait-online --ignore=lo ignoring: lo Event loop failed: Connection timed out root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 ens3 ether off unmanaged 3 sit0 sitoff unmanaged 3 links listed. root@ubuntu:/etc/systemd/system/network-online.target.wants# The system took 120 seconds to complete boot, because wait-online had to finish; and running wait-online from the system afterwards also waits 120 seconds (its default timeout). If there is no configuration for an interface, it's unmanaged (as shown by networkctl), so wait-online should not wait, and simply report that all interfaces are unmanaged, possibly returning an error so we don't reach network-online. FWIW, having wait-online look up configuration might later be useful also to figure out if an interface was configured, but marked as optional (such that it is explicitly not required to be up at boot), or if we want to configure network devices but specify that networkd should *not* bring them online (like "administratively disabled" interfaces in Cisco world using the "shutdown" command). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged
Essentially we are looking for this work flow to function, with or without network devices attached to the system. $ wget http://cloud-images.ubuntu.com/some-disk.img $ qemu-img create -f qcow2 -b some-disk.img my-disk.img $ sudo ~/bin/backdoor-image my-disk.img --user=user1 --password=passw0rd1 $ qemu-system-x86_64 -enable-kvm \ -device virtio-scsi-pci,id=virtio-scsi-xkvm \ -drive file=my.img,id=disk00,if=none,format=qcow2,index=0 \ -device virtio-blk,drive=disk00,serial=my.img \ -m 768 -nodefaults -nographic -serial mon:stdio -echr 0x05 then just login at prompt with 'user1' and 'password1' That does generally work right now, it just has a 120 second-ish timeout on waiting for network devices that configured (and possibly even are not present) to come up. http://paste.ubuntu.com/25833773/ -- 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/1728181 Title: systemd-networkd-wait-online waits when devices are unmanaged Status in systemd package in Ubuntu: Confirmed Bug description: I started a system with cloud-init disabled, etc. and a single real network interface (ens3) that could be configured. That VM has no configuration whatsoever for systemd-networkd, as that would have to have been written by netplan, and cloud-init did not generate netplan config (because it was disabled). So: root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route d-networkd-wait-online --ignore=lo ignoring: lo Event loop failed: Connection timed out root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 ens3 ether off unmanaged 3 sit0 sitoff unmanaged 3 links listed. root@ubuntu:/etc/systemd/system/network-online.target.wants# The system took 120 seconds to complete boot, because wait-online had to finish; and running wait-online from the system afterwards also waits 120 seconds (its default timeout). If there is no configuration for an interface, it's unmanaged (as shown by networkctl), so wait-online should not wait, and simply report that all interfaces are unmanaged, possibly returning an error so we don't reach network-online. FWIW, having wait-online look up configuration might later be useful also to figure out if an interface was configured, but marked as optional (such that it is explicitly not required to be up at boot), or if we want to configure network devices but specify that networkd should *not* bring them online (like "administratively disabled" interfaces in Cisco world using the "shutdown" command). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged
** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1728181 Title: systemd-networkd-wait-online waits when devices are unmanaged Status in systemd package in Ubuntu: Confirmed Bug description: I started a system with cloud-init disabled, etc. and a single real network interface (ens3) that could be configured. That VM has no configuration whatsoever for systemd-networkd, as that would have to have been written by netplan, and cloud-init did not generate netplan config (because it was disabled). So: root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route d-networkd-wait-online --ignore=lo ignoring: lo Event loop failed: Connection timed out root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 ens3 ether off unmanaged 3 sit0 sitoff unmanaged 3 links listed. root@ubuntu:/etc/systemd/system/network-online.target.wants# The system took 120 seconds to complete boot, because wait-online had to finish; and running wait-online from the system afterwards also waits 120 seconds (its default timeout). If there is no configuration for an interface, it's unmanaged (as shown by networkctl), so wait-online should not wait, and simply report that all interfaces are unmanaged, possibly returning an error so we don't reach network-online. FWIW, having wait-online look up configuration might later be useful also to figure out if an interface was configured, but marked as optional (such that it is explicitly not required to be up at boot), or if we want to configure network devices but specify that networkd should *not* bring them online (like "administratively disabled" interfaces in Cisco world using the "shutdown" command). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp