| 2024-04-09 22:03:28 |
Thiago Martins |
bug |
|
|
added bug |
| 2024-04-09 23:14:19 |
Thiago Martins |
bug watch added |
|
https://github.com/NetworkBlockDevice/nbd/issues/156 |
|
| 2024-04-10 16:40:31 |
Athos Ribeiro |
bug task added |
|
nbd |
|
| 2024-04-10 17:30:26 |
Athos Ribeiro |
nbd (Ubuntu): status |
New |
Triaged |
|
| 2024-04-10 17:30:36 |
Athos Ribeiro |
bug |
|
|
added subscriber Ubuntu Server |
| 2024-04-10 17:30:51 |
Athos Ribeiro |
tags |
|
server-todo |
|
| 2024-04-11 00:25:50 |
Bug Watch Updater |
nbd: status |
Unknown |
New |
|
| 2024-04-24 15:32:23 |
Bryce Harrington |
nbd (Ubuntu): assignee |
|
Mitchell Dzurick (mitchdz) |
|
| 2024-04-24 16:42:20 |
Mitchell Dzurick |
nominated for series |
|
Ubuntu Noble |
|
| 2024-04-24 16:42:20 |
Mitchell Dzurick |
bug task added |
|
nbd (Ubuntu Noble) |
|
| 2024-04-25 15:17:02 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~mitchdz/ubuntu/+source/nbd/+git/nbd/+merge/464996 |
|
| 2024-04-25 15:37:31 |
Mitchell Dzurick |
description |
[ Impact ]
NBD users who want to use /etc/nbdtab will face issues when trying to start the NBD Client. Trying to use the `systemd` service also doesn't work.
[ Test Plan ]
Inside a Noble VM (not a container):
# apt update
# apt install -y nbd-client nbd-server
# modprobe nbd
# truncate -s 1T /vol-0.img
# cat > /etc/nbd-server/conf.d/exports.conf << _EOF_
[vol0]
exportname = /vol-0.img
_EOF_
# systemctl restart nbd-server.service
Verify that NBD is working properly:
# nbd-client localhost /dev/nbd0 -name vol0
It should work.
To clean it up:
# nbd-client -d /dev/nbd0
Now, trigger the problem:
# cat >> /etc/nbdtab << _EOF_
nbd0 localhost vol0
_EOF_
# nbd-client nbd0
You should see the error:
# nbd-client nbd0
Error: Socket failed: Connection refused
Further attempts with `systemd` also fail:
# 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 "journalctl -xeu nbd@nbd0.service" for details.
And the logs:
# journalctl -u nbd@nbd0.service -n 25
Apr 09 21:56:17 noble-nbd-1 systemd[1]: nbd@nbd0.service: Dependency Before=dev-nbd0.device ignored (.device units cannot be delayed)
Apr 09 21:56:17 noble-nbd-1 systemd[1]: Starting nbd@nbd0.service - NBD client connection for nbd0...
Apr 09 21:56:17 noble-nbd-1 nbd_client[5698]: Socket failed: Connection refused
Apr 09 21:56:17 noble-nbd-1 nbd-client[5698]: Error: Socket failed: Connection refused
Apr 09 21:56:17 noble-nbd-1 nbd_client[5698]: Exiting.
Apr 09 21:56:17 noble-nbd-1 systemd[1]: nbd@nbd0.service: Main process exited, code=exited, status=1/FAILURE
Apr 09 21:56:17 noble-nbd-1 systemd[1]: nbd@nbd0.service: Failed with result 'exit-code'.
Apr 09 21:56:17 noble-nbd-1 systemd[1]: Failed to start nbd@nbd0.service - NBD client connection for nbd0. |
[ Impact ]
nbdtab uses a port of 0 by default which is not sensible. This means that if you do not set a default port in nbdtab, it will fail.
You will see an error such as: Error: Socket failed: Connection refused
[ Test Plan ]
$ lxc launch ubuntu:noble n-vm --vm
$ lxc shell n-vm
# apt update -y && apt install -y nbd-client nbd-server
# dpkg -s nbd-client | grep Version:
Version: 1:3.26.1-1build1
# modprobe nbd
# truncate -s 1T /vol-0.img
# cat > /etc/nbd-server/conf.d/exports.conf << _EOF_
[vol0]
exportname = /vol-0.img
_EOF_
# systemctl restart nbd-server.service
Verify that NBD is working properly:
# nbd-client localhost /dev/nbd0 -name vol0
It should work.
To clean it up:
# nbd-client -d /dev/nbd0
Now, trigger the problem:
# cat >> /etc/nbdtab << _EOF_
nbd0 localhost vol0
_EOF_
# nbd-client nbd0
You should see the error:
# nbd-client nbd0
Error: Socket failed: Connection refused
Test the fix:
# add-apt-repository -y ppa:mitchdz/lp2060745-nbd-port-fix
# apt update -y && apt upgrade -y
# dpkg -s nbd-client | grep Version:
Version: 1:3.26.1-1ubuntu0.1~noble1
# nbd-client -d /dev/nbd0
< no errors here> |
|
| 2024-04-25 15:37:50 |
Mitchell Dzurick |
summary |
nbd-client fails to connect when using /etc/nbdtab on Ubuntu 24.04 (Noble) |
nbd-client fails to connect Error: Socket failed: Connection refused |
|
| 2024-04-25 16:03:56 |
Mitchell Dzurick |
description |
[ Impact ]
nbdtab uses a port of 0 by default which is not sensible. This means that if you do not set a default port in nbdtab, it will fail.
You will see an error such as: Error: Socket failed: Connection refused
[ Test Plan ]
$ lxc launch ubuntu:noble n-vm --vm
$ lxc shell n-vm
# apt update -y && apt install -y nbd-client nbd-server
# dpkg -s nbd-client | grep Version:
Version: 1:3.26.1-1build1
# modprobe nbd
# truncate -s 1T /vol-0.img
# cat > /etc/nbd-server/conf.d/exports.conf << _EOF_
[vol0]
exportname = /vol-0.img
_EOF_
# systemctl restart nbd-server.service
Verify that NBD is working properly:
# nbd-client localhost /dev/nbd0 -name vol0
It should work.
To clean it up:
# nbd-client -d /dev/nbd0
Now, trigger the problem:
# cat >> /etc/nbdtab << _EOF_
nbd0 localhost vol0
_EOF_
# nbd-client nbd0
You should see the error:
# nbd-client nbd0
Error: Socket failed: Connection refused
Test the fix:
# add-apt-repository -y ppa:mitchdz/lp2060745-nbd-port-fix
# apt update -y && apt upgrade -y
# dpkg -s nbd-client | grep Version:
Version: 1:3.26.1-1ubuntu0.1~noble1
# nbd-client -d /dev/nbd0
< no errors here> |
[ Impact ]
nbdtab uses a port of 0 by default which is not sensible. This means that if you do not set a default port in nbdtab, it will fail.
You will see an error such as: Error: Socket failed: Connection refused
[ Test Plan ]
$ lxc launch ubuntu:noble n-vm --vm
$ lxc shell n-vm
# apt update -y && apt install -y nbd-client nbd-server
# dpkg -s nbd-client | grep Version:
Version: 1:3.26.1-1build1
# modprobe nbd
# truncate -s 1T /vol-0.img
# cat > /etc/nbd-server/conf.d/exports.conf << _EOF_
[vol0]
exportname = /vol-0.img
_EOF_
# systemctl restart nbd-server.service
Verify that NBD is working properly:
# nbd-client localhost /dev/nbd0 -name vol0
It should work.
To clean it up:
# nbd-client -d /dev/nbd0
Now, trigger the problem:
# cat >> /etc/nbdtab << _EOF_
nbd0 localhost vol0
_EOF_
# nbd-client nbd0
You should see the error:
# nbd-client nbd0
Error: Socket failed: Connection refused
Test the fix:
# add-apt-repository -y ppa:mitchdz/lp2060745-nbd-port-fix
# apt update -y && apt upgrade -y
# dpkg -s nbd-client | grep Version:
Version: 1:3.26.1-1ubuntu0.1~noble1
# nbd-client -d /dev/nbd0
< no errors here>
[ Where problems could occur ]
* This changes the default port, so issues using custom ports could arise. This seems unlikely since it is a one line change that should get overridden. |
|
| 2024-04-25 17:28:52 |
Mitchell Dzurick |
nbd (Ubuntu Noble): status |
Triaged |
In Progress |
|
| 2024-04-25 17:28:58 |
Mitchell Dzurick |
nbd (Ubuntu Noble): importance |
Undecided |
High |
|
| 2024-05-02 20:51:12 |
Andreas Hasenack |
nbd (Ubuntu Noble): status |
In Progress |
Fix Committed |
|
| 2024-05-02 20:51:13 |
Andreas Hasenack |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2024-05-02 20:51:16 |
Andreas Hasenack |
bug |
|
|
added subscriber SRU Verification |
| 2024-05-02 20:51:19 |
Andreas Hasenack |
tags |
server-todo |
server-todo verification-needed verification-needed-noble |
|
| 2024-05-04 06:29:39 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~mitchdz/ubuntu/+source/nbd/+git/nbd/+merge/465532 |
|
| 2024-05-07 15:50:26 |
Andreas Hasenack |
nbd (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2024-05-14 16:10:28 |
Launchpad Janitor |
nbd (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2024-05-20 21:16:10 |
Mauricio Faria de Oliveira |
description |
[ Impact ]
nbdtab uses a port of 0 by default which is not sensible. This means that if you do not set a default port in nbdtab, it will fail.
You will see an error such as: Error: Socket failed: Connection refused
[ Test Plan ]
$ lxc launch ubuntu:noble n-vm --vm
$ lxc shell n-vm
# apt update -y && apt install -y nbd-client nbd-server
# dpkg -s nbd-client | grep Version:
Version: 1:3.26.1-1build1
# modprobe nbd
# truncate -s 1T /vol-0.img
# cat > /etc/nbd-server/conf.d/exports.conf << _EOF_
[vol0]
exportname = /vol-0.img
_EOF_
# systemctl restart nbd-server.service
Verify that NBD is working properly:
# nbd-client localhost /dev/nbd0 -name vol0
It should work.
To clean it up:
# nbd-client -d /dev/nbd0
Now, trigger the problem:
# cat >> /etc/nbdtab << _EOF_
nbd0 localhost vol0
_EOF_
# nbd-client nbd0
You should see the error:
# nbd-client nbd0
Error: Socket failed: Connection refused
Test the fix:
# add-apt-repository -y ppa:mitchdz/lp2060745-nbd-port-fix
# apt update -y && apt upgrade -y
# dpkg -s nbd-client | grep Version:
Version: 1:3.26.1-1ubuntu0.1~noble1
# nbd-client -d /dev/nbd0
< no errors here>
[ Where problems could occur ]
* This changes the default port, so issues using custom ports could arise. This seems unlikely since it is a one line change that should get overridden. |
[ Impact ]
nbdtab uses a port of 0 by default which is not sensible. This means that if you do not set a default port in nbdtab, it will fail.
You will see an error such as: Error: Socket failed: Connection refused
[ Test Plan ]
$ lxc launch ubuntu:noble n-vm --vm
$ lxc shell n-vm
# apt update -y && apt install -y nbd-client nbd-server
# dpkg -s nbd-client | grep Version:
Version: 1:3.26.1-1build1
# modprobe nbd
# truncate -s 1T /vol-0.img
# cat > /etc/nbd-server/conf.d/exports.conf << _EOF_
[vol0]
exportname = /vol-0.img
_EOF_
# systemctl restart nbd-server.service
Verify that NBD is working properly:
# nbd-client localhost /dev/nbd0 -name vol0
It should work.
To clean it up:
# nbd-client -d /dev/nbd0
Now, trigger the problem:
# cat >> /etc/nbdtab << _EOF_
nbd0 localhost vol0
_EOF_
# nbd-client nbd0
You should see the error:
# nbd-client nbd0
Error: Socket failed: Connection refused
Test the fix:
# add-apt-repository -y ppa:mitchdz/lp2060745-nbd-port-fix
# apt update -y && apt upgrade -y
# dpkg -s nbd-client | grep Version:
Version: 1:3.26.1-1ubuntu0.1~noble1
# nbd-client /dev/nbd0
< no errors here>
[ Where problems could occur ]
* This changes the default port, so issues using custom ports could arise. This seems unlikely since it is a one line change that should get overridden. |
|
| 2024-05-20 21:24:38 |
Mauricio Faria de Oliveira |
tags |
server-todo verification-needed verification-needed-noble |
server-todo verification-done verification-done-noble |
|
| 2024-05-20 21:32:22 |
Launchpad Janitor |
nbd (Ubuntu Noble): status |
Fix Committed |
Fix Released |
|
| 2024-05-20 21:32:25 |
Mauricio Faria de Oliveira |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2024-05-22 19:55:49 |
Bug Watch Updater |
nbd: status |
New |
Fix Released |
|
