Think this is related:
Now I have a cyclic dependency with winbind. this breaks the start of the 
network entierly (at least for me). Of course I can start network manually, but 
for a headless server that is not really ideal..

Essentially winbind is to be started before nss-user-lookup.target but
nss-user-lookup.target is to be started after nss-user-lookup.target but
winbind is to be started after network.

The solution is probably not start winbind before nss-user-lookup.target


Note it is not possible using systemctl edit winbind because a empty Before= 
line seems to have no effect, so I needed to manually change 
/lib/systemd/winbind.service to get my system back. feels totally wrong to need 
to edit a file in /lib, but currently that's what is needed)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071747

Title:
  netplan causes unresponsive system with certain nsswitch config

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2071747/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to