Thanks for the additional details and for the improved reproducer. I can
reproduce the issue and looks like the steps you identified are right. I
assume this worked at some point, but the issue is also present in Focal
and Bionic.
I don't think this is working as expected, OTOH the RequiredBy= (an
** Description changed:
The `systemd` service for starting the NBD Clients on boot isn't
working.
### Steps to Reproduce:
0. Install NBD
-
apt install nbd-server nbd-client
-
-
1. Prepare an NBD server with a disk image to share. For instance:
-
truncate -s 1T /
** Description changed:
The `systemd` service for starting the NBD Clients on boot isn't
working.
### Steps to Reproduce:
0. Install NBD
-```
-apt install nbd-server nbd-client
-```
+ -
+ apt install nbd-server nbd-client
+ -
+
1. Prepare an NBD server with a dis
I've updated the description to include all the steps necessary to
reproduce the issue on Ubuntu 22.04 (Cloud Image - Server Minimal
install).
This seems to be a `systemd` thing! lol
** Description changed:
The `systemd` service for starting the NBD Clients on boot isn't
working.
### St
I'm testing on Ubuntu 22.04.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054616
Title:
The systemd service for NBD Client doesn't come up on boot
To manage notifications about this bug go to:
h
Hi Mitchell,
No worries at all!
I forgot to mention another step I took:
```
echo nbd > /etc/modules-load.d/nbd.conf
```
Otherwise it won't load the module on boot.
Perhaps there's also a need to `update-initramfs -k all -u`, not 100%
sure.
--
You received this bug notification because you a
Wouter, is my assumption correct that ideally we should see the devices
available on boot if we enable nbd@nbd0?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054616
Title:
The systemd service for
I've been playing around with noble and I've noticed that sometimes if I
try to restart the service right after boot it will fail
root@n-vm:~# systemctl restart nbd@nbd0
Job for nbd@nbd0.service failed because the control process exited with error
code.
See "systemctl status nbd@nbd0.service" and
Thiago,
Apologies if I missed it somewhere, but which Ubuntu release are you
using for your tests?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054616
Title:
The systemd service for NBD Client do
