Description: netplan-configure.service: fix unresolvable network cycle The service needs to be able to lookup the "systemd-network" GID. Initially, this was done by ordering the service After=nss-user-lookup.target. However, this can result in an ordering cycle if nss-user-lookup.target is ordered after some other service that is itself ordered after network-online.target (winbind.service, for example). Since "systemd-network" is created by systemd-sysusers, we can order it after systemd-sysusers.service to ensure that the group already exists and avoid the network cycle. Author: Guilherme Puida Moreira Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2071747 --- --- a/netplan-configure.service +++ b/netplan-configure.service @@ -8,9 +8,9 @@ Conflicts=shutdown.target Before=shutdown.target network-pre.target Before=systemd-networkd.service NetworkManager.service -# Run After=nss-user-lookup.target, to allow lookup of the "systemd-network" GID +# Run After=systemd-sysusers.service, to allow lookup of the "systemd-network" GID # (LP: #2071747) -After=local-fs.target nss-user-lookup.target systemd-udevd-control.socket +After=local-fs.target systemd-sysusers.service systemd-udevd-control.socket [Service] Type=oneshot