| 2020-04-06 20:13:00 |
Rodrigo Barbieri |
bug |
|
|
added bug |
| 2020-04-06 20:22:15 |
Rodrigo Barbieri |
description |
Reproduced in Bionic and Focal, packages 1:1.3.4-2.1ubuntu5.2 and 1:1.3.4-2.5ubuntu3 respectively.
Steps to reproduce:
1) Set up a ISCSI client to a 1GB+ volume, mount it /data and set fstab to mount at boot
2) Create a folder in /data like /data/dir1 and set up /etc/exports to export it
3) Reboot
4) Notice nfs-server does not start. Check journalctl and see it was because of "exportfs -r" returning -1 because /data/dir1 is not available.
In Xenial (1:1.2.8-9ubuntu12.2), exportfs always returns 0, so this bug is not present there.
This can be workaroundable in two ways:
1) Editing nfs-server.service and adding "-" in "ExecStartPre=/usr/sbin/exportfs -r" to be "ExecStartPre=-/usr/sbin/exportfs -r". This will retain xenial behavior.
2) Editing nfs-server.service and removing "Before=remote-fs-pre.target" and adding "RequiresMountsFor=/data". This will cause the systemd service load ordering to change, and nfs-server will wait for /data to be available.
#2 is the upstream approach with commit [0] where this new comment identifies mount dependencies and automatically sets up RequiresMountFor.
[0] http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=4776bd0599420f9d073c9e2601ed438062dccd19 |
Reproduced in Bionic and Focal, packages 1:1.3.4-2.1ubuntu5.2 and 1:1.3.4-2.5ubuntu3 respectively.
Steps to reproduce:
1) Set up a ISCSI client to a 1GB+ volume, mount it in /data and set fstab to mount at boot
2) Create a folder in /data like /data/dir1 and set up /etc/exports to export it
3) Reboot
4) Notice nfs-server does not start. Check journalctl and see it was because of "exportfs -r" returning -1 because /data/dir1 is not available.
In Xenial (1:1.2.8-9ubuntu12.2), exportfs always returns 0, so this bug is not present there.
This can be workaroundable in two ways:
1) Editing nfs-server.service and adding "-" in "ExecStartPre=/usr/sbin/exportfs -r" to be "ExecStartPre=-/usr/sbin/exportfs -r". This will retain xenial behavior.
2) Editing nfs-server.service and removing "Before=remote-fs-pre.target" and adding "RequiresMountsFor=/data". This will cause the systemd service load ordering to change, and nfs-server will wait for /data to be available.
#2 is the upstream approach with commit [0] where this new comment identifies mount dependencies and automatically sets up RequiresMountFor.
[0] http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=4776bd0599420f9d073c9e2601ed438062dccd19 |
|
| 2020-04-15 10:50:39 |
Rodrigo Barbieri |
tags |
|
sts |
|
| 2020-04-27 12:18:37 |
Rodrigo Barbieri |
summary |
nfsd doesn't start if exports depend on mount |
[SRU] nfsd doesn't start if exports depend on mount |
|
| 2020-04-27 12:18:49 |
Rodrigo Barbieri |
nfs-utils (Ubuntu): assignee |
|
Rodrigo Barbieri (rodrigo-barbieri2010) |
|
| 2020-04-27 12:19:04 |
Rodrigo Barbieri |
nfs-utils (Ubuntu): status |
New |
Fix Committed |
|
| 2020-04-28 19:41:41 |
Rodrigo Barbieri |
description |
Reproduced in Bionic and Focal, packages 1:1.3.4-2.1ubuntu5.2 and 1:1.3.4-2.5ubuntu3 respectively.
Steps to reproduce:
1) Set up a ISCSI client to a 1GB+ volume, mount it in /data and set fstab to mount at boot
2) Create a folder in /data like /data/dir1 and set up /etc/exports to export it
3) Reboot
4) Notice nfs-server does not start. Check journalctl and see it was because of "exportfs -r" returning -1 because /data/dir1 is not available.
In Xenial (1:1.2.8-9ubuntu12.2), exportfs always returns 0, so this bug is not present there.
This can be workaroundable in two ways:
1) Editing nfs-server.service and adding "-" in "ExecStartPre=/usr/sbin/exportfs -r" to be "ExecStartPre=-/usr/sbin/exportfs -r". This will retain xenial behavior.
2) Editing nfs-server.service and removing "Before=remote-fs-pre.target" and adding "RequiresMountsFor=/data". This will cause the systemd service load ordering to change, and nfs-server will wait for /data to be available.
#2 is the upstream approach with commit [0] where this new comment identifies mount dependencies and automatically sets up RequiresMountFor.
[0] http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=4776bd0599420f9d073c9e2601ed438062dccd19 |
Reproduced in Bionic and Focal, packages 1:1.3.4-2.1ubuntu5.2 and 1:1.3.4-2.5ubuntu3 respectively.
Steps to reproduce:
1) Set up a ISCSI client to a 1GB+ volume, mount it in /data and set fstab to mount at boot
2) Create a folder in /data like /data/dir1 and set up /etc/exports to export it
3) Reboot
4) Notice nfs-server does not start. Check journalctl and see it was because of "exportfs -r" returning -1 because /data/dir1 is not available.
In Xenial (1:1.2.8-9ubuntu12.2), exportfs always returns 0, so this bug is not present there.
This can be workaroundable in two ways:
1) Editing nfs-server.service and adding "-" in "ExecStartPre=/usr/sbin/exportfs -r" to be "ExecStartPre=-/usr/sbin/exportfs -r". This will retain xenial behavior.
2) Editing nfs-server.service and removing "Before=remote-fs-pre.target" and adding "RequiresMountsFor=/data". This will cause the systemd service load ordering to change, and nfs-server will wait for /data to be available.
#2 is the upstream approach with commit [0] where this new comment identifies mount dependencies and automatically sets up RequiresMountFor.
[0] http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=4776bd0599420f9d073c9e2601ed438062dccd19
=======================================================================
[Impact]
Users attempting to export folders from iSCSI or any remote mounted filesystem will experience their exports not being available at system start up, requiring workarounds or manual intervention.
[Test case]
1. Reproducing the bug:
1a. Set up a ISCSI client to a 1GB+ volume
1b. Format /dev/<device> using mkfs.xfs
1c. Mount it in /data and set fstab as follows to mount at boot
UUID="<uuid_from_blkid>" /data xfs defaults,auto,_netdev 0 0
1d. Create a folder in /data like /data/dir1 and set permissions as follows
chmod 777 /data/dir1
chown nobody:nogroup /data/dir1
1e. Set up /etc/exports as follows to export it
data/dir1 *(rw,async,root_squash,subtree_check)
1f. Reboot
1g. Notice nfs-server does not start. Running "showmount -e" displays error.
2. No cleanup necessary
3. Install the updated package that contains the fix
4. Confirming the fix:
4a. Reboot
4b. Notice nfs-server starts sucessfully, "showmount -e" displays the exports.
[Regression Potential]
Regression potential is minimal. The dependency commit only moves code around and the actual fix only introduces an external systemd-generator without changing actual pre-existing code.
I tested and confirmed that the fix introduced [0] also covers the fix removed [1], so there should not be any regression on this particular code change as well.
[1] http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=1e41488f428cd36b200b48b84d31446e38dfdc50
[Other Info] |
|
| 2020-04-29 19:41:03 |
Rodrigo Barbieri |
nominated for series |
|
Ubuntu Eoan |
|
| 2020-04-29 19:41:03 |
Rodrigo Barbieri |
bug task added |
|
nfs-utils (Ubuntu Eoan) |
|
| 2020-04-29 19:41:03 |
Rodrigo Barbieri |
nominated for series |
|
Ubuntu Focal |
|
| 2020-04-29 19:41:03 |
Rodrigo Barbieri |
bug task added |
|
nfs-utils (Ubuntu Focal) |
|
| 2020-04-29 19:41:03 |
Rodrigo Barbieri |
nominated for series |
|
Ubuntu Bionic |
|
| 2020-04-29 19:41:03 |
Rodrigo Barbieri |
bug task added |
|
nfs-utils (Ubuntu Bionic) |
|
| 2020-04-29 19:41:31 |
Rodrigo Barbieri |
nfs-utils (Ubuntu Focal): status |
New |
In Progress |
|
| 2020-04-29 19:43:05 |
Rodrigo Barbieri |
attachment added |
|
lp1871214_focal.debdiff https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+attachment/5363647/+files/lp1871214_focal.debdiff |
|
| 2020-04-29 19:46:27 |
Rodrigo Barbieri |
bug |
|
|
added subscriber STS Sponsors |
| 2020-04-29 19:55:53 |
Rodrigo Barbieri |
nominated for series |
|
Ubuntu Groovy |
|
| 2020-04-29 19:55:53 |
Rodrigo Barbieri |
bug task added |
|
nfs-utils (Ubuntu Groovy) |
|
| 2020-04-29 19:57:14 |
Rodrigo Barbieri |
attachment removed |
lp1871214_focal.debdiff https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+attachment/5363647/+files/lp1871214_focal.debdiff |
|
|
| 2020-04-29 19:58:49 |
Rodrigo Barbieri |
attachment added |
|
lp1871214_focal.debdiff https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+attachment/5363649/+files/lp1871214_focal.debdiff |
|
| 2020-04-29 19:59:52 |
Rodrigo Barbieri |
attachment added |
|
lp1871214_groovy.debdiff https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+attachment/5363650/+files/lp1871214_groovy.debdiff |
|
| 2020-04-30 15:47:30 |
Dariusz Gadomski |
tags |
sts |
sts sts-sponsor-dgadomski |
|
| 2020-04-30 15:48:15 |
Dan Streetman |
bug |
|
|
added subscriber Dan Streetman |
| 2020-05-13 20:51:06 |
Guilherme G. Piccoli |
bug |
|
|
added subscriber Guilherme G. Piccoli |
| 2020-05-28 16:03:37 |
Dan Streetman |
nfs-utils (Ubuntu Groovy): status |
Fix Committed |
In Progress |
|
| 2020-05-28 16:03:41 |
Dan Streetman |
nfs-utils (Ubuntu Eoan): status |
New |
In Progress |
|
| 2020-05-28 16:03:43 |
Dan Streetman |
nfs-utils (Ubuntu Bionic): status |
New |
In Progress |
|
| 2020-05-28 16:04:01 |
Dan Streetman |
nfs-utils (Ubuntu Focal): assignee |
|
Rodrigo Barbieri (rodrigo-barbieri2010) |
|
| 2020-05-28 16:04:08 |
Dan Streetman |
nfs-utils (Ubuntu Eoan): assignee |
|
Rodrigo Barbieri (rodrigo-barbieri2010) |
|
| 2020-05-28 16:04:16 |
Dan Streetman |
nfs-utils (Ubuntu Bionic): assignee |
|
Rodrigo Barbieri (rodrigo-barbieri2010) |
|
| 2020-05-28 16:04:19 |
Dan Streetman |
nfs-utils (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2020-05-28 16:04:20 |
Dan Streetman |
nfs-utils (Ubuntu Eoan): importance |
Undecided |
Medium |
|
| 2020-05-28 16:04:23 |
Dan Streetman |
nfs-utils (Ubuntu Focal): importance |
Undecided |
Medium |
|
| 2020-05-28 16:04:24 |
Dan Streetman |
nfs-utils (Ubuntu Groovy): importance |
Undecided |
Medium |
|
| 2020-05-29 02:05:18 |
Launchpad Janitor |
nfs-utils (Ubuntu Groovy): status |
In Progress |
Fix Released |
|
| 2020-06-10 09:58:02 |
Timo Aaltonen |
nfs-utils (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2020-06-10 09:58:04 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-06-10 09:58:07 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2020-06-10 09:58:13 |
Timo Aaltonen |
tags |
sts sts-sponsor-dgadomski |
sts sts-sponsor-dgadomski verification-needed verification-needed-focal |
|
| 2020-06-16 16:13:35 |
Rodrigo Barbieri |
description |
Reproduced in Bionic and Focal, packages 1:1.3.4-2.1ubuntu5.2 and 1:1.3.4-2.5ubuntu3 respectively.
Steps to reproduce:
1) Set up a ISCSI client to a 1GB+ volume, mount it in /data and set fstab to mount at boot
2) Create a folder in /data like /data/dir1 and set up /etc/exports to export it
3) Reboot
4) Notice nfs-server does not start. Check journalctl and see it was because of "exportfs -r" returning -1 because /data/dir1 is not available.
In Xenial (1:1.2.8-9ubuntu12.2), exportfs always returns 0, so this bug is not present there.
This can be workaroundable in two ways:
1) Editing nfs-server.service and adding "-" in "ExecStartPre=/usr/sbin/exportfs -r" to be "ExecStartPre=-/usr/sbin/exportfs -r". This will retain xenial behavior.
2) Editing nfs-server.service and removing "Before=remote-fs-pre.target" and adding "RequiresMountsFor=/data". This will cause the systemd service load ordering to change, and nfs-server will wait for /data to be available.
#2 is the upstream approach with commit [0] where this new comment identifies mount dependencies and automatically sets up RequiresMountFor.
[0] http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=4776bd0599420f9d073c9e2601ed438062dccd19
=======================================================================
[Impact]
Users attempting to export folders from iSCSI or any remote mounted filesystem will experience their exports not being available at system start up, requiring workarounds or manual intervention.
[Test case]
1. Reproducing the bug:
1a. Set up a ISCSI client to a 1GB+ volume
1b. Format /dev/<device> using mkfs.xfs
1c. Mount it in /data and set fstab as follows to mount at boot
UUID="<uuid_from_blkid>" /data xfs defaults,auto,_netdev 0 0
1d. Create a folder in /data like /data/dir1 and set permissions as follows
chmod 777 /data/dir1
chown nobody:nogroup /data/dir1
1e. Set up /etc/exports as follows to export it
data/dir1 *(rw,async,root_squash,subtree_check)
1f. Reboot
1g. Notice nfs-server does not start. Running "showmount -e" displays error.
2. No cleanup necessary
3. Install the updated package that contains the fix
4. Confirming the fix:
4a. Reboot
4b. Notice nfs-server starts sucessfully, "showmount -e" displays the exports.
[Regression Potential]
Regression potential is minimal. The dependency commit only moves code around and the actual fix only introduces an external systemd-generator without changing actual pre-existing code.
I tested and confirmed that the fix introduced [0] also covers the fix removed [1], so there should not be any regression on this particular code change as well.
[1] http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=1e41488f428cd36b200b48b84d31446e38dfdc50
[Other Info] |
Reproduced in Bionic and Focal, packages 1:1.3.4-2.1ubuntu5.2 and 1:1.3.4-2.5ubuntu3 respectively.
Steps to reproduce:
1) Set up a ISCSI client to a 1GB+ volume, mount it in /data and set fstab to mount at boot
2) Create a folder in /data like /data/dir1 and set up /etc/exports to export it
3) Reboot
4) Notice nfs-server does not start. Check journalctl and see it was because of "exportfs -r" returning -1 because /data/dir1 is not available.
In Xenial (1:1.2.8-9ubuntu12.2), exportfs always returns 0, so this bug is not present there.
This can be workaroundable in two ways:
1) Editing nfs-server.service and adding "-" in "ExecStartPre=/usr/sbin/exportfs -r" to be "ExecStartPre=-/usr/sbin/exportfs -r". This will retain xenial behavior.
2) Editing nfs-server.service and removing "Before=remote-fs-pre.target" and adding "RequiresMountsFor=/data". This will cause the systemd service load ordering to change, and nfs-server will wait for /data to be available.
#2 is the upstream approach with commit [0] where this new comment identifies mount dependencies and automatically sets up RequiresMountFor.
[0] http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=4776bd0599420f9d073c9e2601ed438062dccd19
=======================================================================
[Impact]
Users attempting to export folders from iSCSI or any remote mounted filesystem will experience their exports not being available at system start up, requiring workarounds or manual intervention.
[Test case]
1. Reproducing the bug:
1a. Set up a ISCSI client to a 1GB+ volume
1b. Format /dev/<device> using mkfs.xfs
1c. Mount it in /data and set fstab as follows to mount at boot
UUID="<uuid_from_blkid>" /data xfs defaults,auto,_netdev 0 0
1d. Create a folder in /data like /data/dir1 and set permissions as follows
chmod 777 /data/dir1
chown nobody:nogroup /data/dir1
1e. Set up /etc/exports as follows to export it
/data/dir1 *(rw,async,root_squash,subtree_check)
1f. Reboot
1g. Notice nfs-server does not start. Running "showmount -e" displays error.
2. No cleanup necessary
3. Install the updated package that contains the fix
4. Confirming the fix:
4a. Reboot
4b. Notice nfs-server starts sucessfully, "showmount -e" displays the exports.
[Regression Potential]
Regression potential is minimal. The dependency commit only moves code around and the actual fix only introduces an external systemd-generator without changing actual pre-existing code.
I tested and confirmed that the fix introduced [0] also covers the fix removed [1], so there should not be any regression on this particular code change as well.
[1] http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=1e41488f428cd36b200b48b84d31446e38dfdc50
[Other Info] |
|
| 2020-06-16 22:11:12 |
Rodrigo Barbieri |
attachment added |
|
validation_nfs_utils_focal.txt https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1871214/+attachment/5384559/+files/validation_nfs_utils_focal.txt |
|
| 2020-06-16 22:12:55 |
Rodrigo Barbieri |
tags |
sts sts-sponsor-dgadomski verification-needed verification-needed-focal |
sts sts-sponsor-dgadomski verification-done verification-done-focal |
|
| 2020-06-17 16:36:35 |
Robie Basak |
nfs-utils (Ubuntu Bionic): status |
In Progress |
Incomplete |
|
| 2020-06-17 16:36:37 |
Robie Basak |
nfs-utils (Ubuntu Eoan): status |
In Progress |
Incomplete |
|
| 2020-06-18 09:01:08 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2020-06-18 09:01:06 |
Launchpad Janitor |
nfs-utils (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2020-06-28 20:02:43 |
Rodrigo Barbieri |
nfs-utils (Ubuntu Eoan): status |
Incomplete |
Won't Fix |
|
| 2020-06-28 20:02:51 |
Rodrigo Barbieri |
nfs-utils (Ubuntu Bionic): status |
Incomplete |
Won't Fix |
|
