Public bug reported:
Ubuntu 26.04 LTS
nbd-client 1:3.26.1-6.1ubuntu2
The nbd-client userspace process dies immediately when invoked from
initrd, unless the "-nonetlink" parameter is added
To reproduce:
- Configure root on nbd
- Boot with break=mount and run /scripts manually.
- After running /scripts/local-top/nbd you'll find that nbd0 exists but
nbd-client process has already left the chat.
After -nonetlink is added the systemd-mark does the right thing and nbd-
client remains after systemd is started up.
The out of date documentation and pre-systemd (sendsigs.omit.d
references) stuff in /etc/init.d/nbd-client make it considerably less
clear where things are breaking.
Apparently future nbd-client versions will remove -nonetlink, so still
need to get to the bottom of this fault (or perhaps it's already fixed
upstream).
** Affects: nbd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2165126
Title:
nbdroot on resolute: nbd-client process dies immediately, nbd device
will not reconnect after server restart or network interruption
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2165126/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
