Merge ~ahasenack/ubuntu/+source/nfs-utils:bionic-thread-safety-gssd-1927745 into ubuntu/+source/nfs-utils:ubuntu/bionic-devel
Status: | Merged |
---|---|
Approved by: | Andreas Hasenack |
Approved revision: | 5a5c61e7c66b1f61826313692d359985eceee2d1 |
Merged at revision: | 5a5c61e7c66b1f61826313692d359985eceee2d1 |
Proposed branch: | ~ahasenack/ubuntu/+source/nfs-utils:bionic-thread-safety-gssd-1927745 |
Merge into: | ubuntu/+source/nfs-utils:ubuntu/bionic-devel |
Diff against target: |
174 lines (+146/-0) 4 files modified
debian/changelog (+9/-0) debian/patches/0010-gssd-replace-non-thread-safe-strtok-with-strsep.patch (+42/-0) debian/patches/0011-gssd-Duplicate-the-upcall-string-for-error-messages.patch (+93/-0) debian/patches/series (+2/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Sergio Durigan Junior (community) | Approve | ||
Canonical Server | Pending | ||
Review via email: mp+402515@code.launchpad.net |
Description of the change
The linked bug has the SRU template filled in.
PPA with test packages: https:/
Note: it's a race condition and the supplied test doesn't always catch it. Sometimes I get it right away, other times I leave it running for an hour and nothing happens.
I had more success with reproducing the problem once I increased the number of cores available to the VM. I used 4.
This involves NFSv4 with kerberos, but I think I narrowed the setup down enough for an SRU test case. I may update the test case a bit still if I find a way to make the error happen more quickly, or more realiably.
I took the same patches as debian, which are in our focal+ packages, and just updated the DEP3 header with a link to this bug, and updated the "Last-Updated" field.
DEP8 passed: client: [------ ------- ------- --- t.REnxBo/ build.2Ib/ real-tree/ debian/ tests/local- server- client 2> >(tee -a /tmp/autopkgtes t.REnxBo/ local-server- client- stderr >&2) > >(tee -a /tmp/autopkgtes t.REnxBo/ local-server- client- stdout) virt-ssh: WARNING: ssh connection failed. Retrying in 3 seconds... vers=4. 2,rsize= 262144, wsize=262144, namlen= 255,hard, proto=tcp, timeo=600, retrans= 2,sec=sys, clientaddr= 127.0.0. 1,local_ lock=none, addr=127. 0.0.1) vers=4. 2,rsize= 262144, wsize=262144, namlen= 255,hard, proto=tcp, timeo=600, retrans= 2,sec=sys, clientaddr= 127.0.0. 1,local_ lock=none, addr=127. 0.0.1) client: ------- ------- ------- --] client: - - - - - - - - - - results - - - - - - - - - - @@@@@@@ @@@@@@ summary br.archive. ubuntu. com/ubuntu bionic InRelease br.archive. ubuntu. com/ubuntu bionic-updates InRelease br.archive. ubuntu. com/ubuntu bionic-backports InRelease br.archive. ubuntu. com/ubuntu bionic-security InRelease
autopkgtest [15:19:11]: test local-server-
bash: line 1: 29878 Killed /tmp/autopkgtes
autopkgtest [15:19:11]: test process requested reboot with marker boot1
autopkgtest-
localhost:/home on /mnt/nfs_home type nfs4 (rw,relatime,
localhost:/var/log on /mnt/nfs_log type nfs4 (rw,relatime,
autopkgtest [15:19:28]: test local-server-
autopkgtest [15:19:28]: test local-server-
local-server-client PASS
autopkgtest [15:19:28]: @@@@@@@
local-server-client PASS
autopkgtest [15:19:28]: Binaries: resetting testbed apt configuration
Hit:1 http://
Hit:2 http://
Hit:3 http://
Hit:4 http://
Reading package lists...
I thought that "Killed" message odd, but it's also present in autopkgtest. ubuntu. com runs: https:/ /autopkgtest. ubuntu. com/results/ autopkgtest- bionic/ bionic/ amd64/n/ nfs-utils/ 20201210_ 022246_ 2218d@/ log.gz
I think it's from the reboot.