Hello and thanks for this bug report. I had a quick look at /lib/systemd/system/nbd@.service, and the [Install] section shows that the nbd@*.service units are not meant to just be started automatically, but when a dev-*.device is created:
and I believe there are udev rules handling those devices. In other words, I believe we need a more complete picture of what issue to triage this as a bug and begin working on it. Could you please provide a minimal but complete set of steps to configure an Ubuntu system so that the problem reproduces? Using the same system as client and server should be enough, similar to what has been done in LP: #2054470.
Hello and thanks for this bug report. I had a quick look at /lib/systemd/ system/ nbd@.service, and the [Install] section shows that the nbd@*.service units are not meant to just be started automatically, but when a dev-*.device is created:
[Install] dev-%i. device dev-%ip1. device
RequiredBy=
RequiredBy=
[...]
and I believe there are udev rules handling those devices. In other words, I believe we need a more complete picture of what issue to triage this as a bug and begin working on it. Could you please provide a minimal but complete set of steps to configure an Ubuntu system so that the problem reproduces? Using the same system as client and server should be enough, similar to what has been done in LP: #2054470.
Thanks