[Touch-packages] [Bug 1975587] Re: systemd: fix test-execute autotest failure with kernel 5.15 in focal
** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1975587 Title: systemd: fix test-execute autotest failure with kernel 5.15 in focal Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: In Progress Bug description: [Impact] test-execute autotest is failing in focal with kernel 5.15. This is because the following kernel commit changed the ABI for ioprio: e70344c05995 ("block: fix default IO priority handling") Previously setting IOPRIO_CLASS_NONE for a process would report IOPRIO_CLASS_NONE back. But starting with 5.15 it reports IOPRIO_CLASS_BE instead. [Test case] Run systemd autopkgtest and check for the test-execute result. [Fix] Change test/test-execute/exec-ioschedulingclass-none.service to recognize both "none" and "best-effort" as valid returned strings from ionice. This change is already available in jammy and above. [Regression potential] We may see regressions in systemd autopkgtest, we won't introduce any potential regressions in systemd itself, because this is only affecting the specific unit test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1975587] Re: systemd: fix test-execute autotest failure with kernel 5.15 in focal
** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1975587 Title: systemd: fix test-execute autotest failure with kernel 5.15 in focal Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: In Progress Bug description: [Impact] test-execute autotest is failing in focal with kernel 5.15. This is because the following kernel commit changed the ABI for ioprio: e70344c05995 ("block: fix default IO priority handling") Previously setting IOPRIO_CLASS_NONE for a process would report IOPRIO_CLASS_NONE back. But starting with 5.15 it reports IOPRIO_CLASS_BE instead. [Test case] Run systemd autopkgtest and check for the test-execute result. [Fix] Change test/test-execute/exec-ioschedulingclass-none.service to recognize both "none" and "best-effort" as valid returned strings from ionice. This change is already available in jammy and above. [Regression potential] We may see regressions in systemd autopkgtest, we won't introduce any potential regressions in systemd itself, because this is only affecting the specific unit test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1933090] Re: systemd/245.4-4ubuntu3.6 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** Changed in: linux-hwe-5.15 (Ubuntu) Status: New => Invalid ** Changed in: linux-hwe-5.15 (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1933090 Title: systemd/245.4-4ubuntu3.6 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: Won't Fix Status in linux-hwe-5.15 package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in linux-hwe-5.11 source package in Focal: Won't Fix Status in linux-hwe-5.15 source package in Focal: Invalid Status in systemd source package in Focal: Triaged Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz In arm64, ppc64el and s390x, 'root-unittests' fails with: /* test_protect_sysctl */ Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311, function test_protect_sysctl(). A borting. sysctlseccomp terminated by signal ABRT. Assertion 'wait_for_terminate_and_check("sysctlseccomp", pid, WAIT_LOG) == EXIT_SUCCESS' failed at s rc/test/test-seccomp.c:324, function test_protect_sysctl(). Aborting. FAIL: test-seccomp (code: 134) In amd64, 'upstream' also fails on 'TEST-24-UNIT-TESTS', which apparently is caused by the same 'test-seccomp.c:311' assertion failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884024] Re: lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4
Spotted also with bionic/linux-hwe-5.4 5.4.0-73.82~18.04.1. ** Tags added: hwe ** Tags added: hwe-5.4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1884024 Title: lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4 Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Fix Committed Bug description: Issue found on with 5.4.0-1016.16~18.04.1-oracle on both VM.Standard2.1 and VM.Standard2.16 Test failed with: FAIL: lxc-tests: lxc-test-device-add-remove (1s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... This issue can be found on oracle : 5.4.0-1011.11~18.04.1 on VM.Standard2.16 but passed on VM.Standard2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1884024/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1930082] Re: systemd/247.3-3ubuntu3 ADT test failure with linux-raspi H/G/F
This seems to be a testbed issue and not a linux-raspi kernel bug. Looking at the logs, the first reboot with the latest raspi kernel installed is successful. However, some subsequent reboot will fail. Looking at the openstack nova console logs, we can see that the testbed is running the generic arm64 kernel: --- nova console-log 225fbcdf-170f-4f77-bf46-1435821e0776 (adt-hirsute-arm64-systemd-20210528-035426) -- [2J[01;01H[=3h[2J[01;01H[2J[01;01H[=3h[2J[01;01H[2J[01;01H[=3h[2J[01;01H[0m[35m[40m[0m[37m[40merror: no suitable video mode found. EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable, KASLR will be disabled EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... [0.00] Booting Linux on physical CPU 0x00 [0x503f0002] [0.00] Linux version 5.11.0-17-generic (buildd@bos02-arm64-057) (gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.36.1) #18-Ubuntu SMP Thu May 6 17:29:33 UTC 2021 (Ubuntu 5.11.0-17.18-generic 5.11.12) When the system is rebooted, it fails to come back and hangs at: [ 145.624340] reboot: Restarting system [2J[01;01H[=3h[2J[01;01H[2J[01;01H[=3h[2J[01;01H[2J[01;01H[=3h[2J[01;01H[0m[35m[40m[0m[37m[40merror: no suitable video mode found. EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable, KASLR will be disabled EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1930082 Title: systemd/247.3-3ubuntu3 ADT test failure with linux-raspi H/G/F Status in linux-raspi package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux-raspi/5.11.0-1009.10 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on Hirsute/raspi: arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/s/systemd/20210528_100011_6f6f0@/log.gz Testing failed on Groovy/raspi: arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-groovy/groovy/arm64/s/systemd/20210528_084522_9b779@/log.gz Testing failed on Focal/raspi: arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/s/systemd/20210528_092727_7c33b@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1930082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1917601] Re: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.8.0-45.51
This issue is also affecting kernel regression tests. ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1917601 Title: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.8.0-45.51 Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Confirmed Status in lxc source package in Groovy: Confirmed Bug description: We seem to get failed dep8 testing on lxc in Groovy for a while. What we are interested in is knowing whether this is known problems in the testing or something that waits on kernel fixes (who would be driving those if this is the case). Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/l/lxc/20210224_161232_5c8ac@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/arm64/l/lxc/20210224_202135_e7aed@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/ppc64el/l/lxc/20210224_172418_73aab@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/s390x/l/lxc/20210224_164056_06e00@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1917601/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1933090] [NEW] systemd/245.4-4ubuntu3.7 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Public bug reported: This is a scripted bug report about ADT failures while running systemd tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz ** Affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: linux-hwe-5.11 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-hwe-5.11 (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1933090 Title: systemd/245.4-4ubuntu3.7 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: New Status in systemd package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: New Status in systemd source package in Focal: New Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1933090] Re: systemd/245.4-4ubuntu3.7 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
The tests actually ran with systemd/245.4-4ubuntu3.6 and not with systemd/245.4-4ubuntu3.7. We are having some issues with the hwe-5.11 meta packages which caused the tests with 3.7 to be run with the wrong kernel. ** Description changed: This is a scripted bug report about ADT failures while running systemd tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: - armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz + amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz + armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz + ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz + s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz + + In arm64, ppc64el and s390x, 'root-unittests' fails with: + + /* test_protect_sysctl */ + Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311, function test_protect_sysctl(). A + borting. + sysctlseccomp terminated by signal ABRT. + Assertion 'wait_for_terminate_and_check("sysctlseccomp", pid, WAIT_LOG) == EXIT_SUCCESS' failed at s + rc/test/test-seccomp.c:324, function test_protect_sysctl(). Aborting. + FAIL: test-seccomp (code: 134) + + In amd64, 'upstream' also fails on 'TEST-24-UNIT-TESTS', which + apparently is caused by the same 'test-seccomp.c:311' assertion failure. ** Summary changed: - systemd/245.4-4ubuntu3.7 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1 + systemd/245.4-4ubuntu3.6 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1933090 Title: systemd/245.4-4ubuntu3.6 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: New Status in systemd package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: New Status in systemd source package in Focal: New Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz In arm64, ppc64el and s390x, 'root-unittests' fails with: /* test_protect_sysctl */ Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311, function test_protect_sysctl(). A borting. sysctlseccomp terminated by signal ABRT. Assertion 'wait_for_terminate_and_check("sysctlseccomp", pid, WAIT_LOG) == EXIT_SUCCESS' failed at s rc/test/test-seccomp.c:324, function test_protect_sysctl(). Aborting. FAIL: test-seccomp (code: 134) In amd64, 'upstream' also fails on 'TEST-24-UNIT-TESTS', which apparently is caused by the same 'test-seccomp.c:311' assertion failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965293] [NEW] systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-37.42
Public bug reported: This is a scripted bug report about ADT failures while running systemd tests for linux/5.13.0-37.42 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220317_104248_4bc6b@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220316_141606_ab727@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220317_110143_b6ced@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/s/systemd/20220317_103032_3d4bf@/log.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Impish) Importance: Undecided Status: Incomplete ** Affects: systemd (Ubuntu Impish) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Impish) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1965293 Title: systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-37.42 Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in linux source package in Impish: Incomplete Status in systemd source package in Impish: New Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux/5.13.0-37.42 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220317_104248_4bc6b@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220316_141606_ab727@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220317_110143_b6ced@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/s/systemd/20220317_103032_3d4bf@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965293/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965293] Re: systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-37.42
** Description changed: This is a scripted bug report about ADT failures while running systemd tests for linux/5.13.0-37.42 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: - amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220317_104248_4bc6b@/log.gz - arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220316_141606_ab727@/log.gz - ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220317_110143_b6ced@/log.gz - s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/s/systemd/20220317_103032_3d4bf@/log.gz + amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220317_104248_4bc6b@/log.gz + arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220316_141606_ab727@/log.gz + ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220317_110143_b6ced@/log.gz + s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/s/systemd/20220317_103032_3d4bf@/log.gz + + The "tests-in-lxd" testcase is failing with all kernels in Impish: + + test_no_failed (__main__.ServicesTest) + No failed units ... journal for failed service snap-lxd-22662.mount --- + -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 10:01:49 UTC. -- + Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for lxd, revision 22662... + Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[91]: mount: /snap/lxd/22662: mount failed: Operation not permitted. + Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: Mount process exited, code=exited, status=1/FAILURE + Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: Failed with result 'exit-code'. + Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit for lxd, revision 22662. + journal for failed service snap-snapd-15177.mount --- + -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 10:01:49 UTC. -- + Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for snapd, revision 15177... + Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[92]: mount: /snap/snapd/15177: mount failed: Operation not permitted. + Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: Mount process exited, code=exited, status=1/FAILURE + Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: Failed with result 'exit-code'. + Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit for snapd, revision 15177. + FAIL + [...] + == + FAIL: test_no_failed (__main__.ServicesTest) + No failed units + -- + Traceback (most recent call last): + File "/tmp/autopkgtest.HBv169/build.sBq/real-tree/debian/tests/boot-and-services", line 69, in test_no_failed + self.assertEqual(failed, []) + AssertionError: Lists differ: ['snap-lxd-22662.mount loaded failed fai[119 chars]177'] != [] + + First list contains 2 additional elements. + First extra element 0: + 'snap-lxd-22662.mount loaded failed failed Mount unit for lxd, revision 22662' + + + [] + - ['snap-lxd-22662.mount loaded failed failed Mount unit for lxd, revision ' + - '22662', + - 'snap-snapd-15177.mount loaded failed failed Mount unit for snapd, revision ' + - '15177'] + + + This testcase started to fail with the latest re-spin of the kernels (uploaded on mar-16), however the only patch applied between the previous kernels and the current ones is a CVE fix which is unlikely to be causing this failure: + + "ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()" + https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/impish/commit/?id=da5043b3ed2889300211ba35d5a7d2f3b9255d1b -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1965293 Title: systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with linux/5.13.0-37.42 Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in linux source package in Impish: Incomplete Status in systemd source package in Impish: New Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux/5.13.0-37.42 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/
[Touch-packages] [Bug 1965293] Re: systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with linux/5.13.0-37.42
** Summary changed: - systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-37.42 + systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with linux/5.13.0-37.42 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1965293 Title: systemd/248.3-1ubuntu8.2 ADT test failure (tests-in-lxd) with linux/5.13.0-37.42 Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in linux source package in Impish: Incomplete Status in systemd source package in Impish: New Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux/5.13.0-37.42 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220317_104248_4bc6b@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220316_141606_ab727@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220317_110143_b6ced@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/s/systemd/20220317_103032_3d4bf@/log.gz The "tests-in-lxd" testcase is failing with all kernels in Impish: test_no_failed (__main__.ServicesTest) No failed units ... journal for failed service snap-lxd-22662.mount --- -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 10:01:49 UTC. -- Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for lxd, revision 22662... Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[91]: mount: /snap/lxd/22662: mount failed: Operation not permitted. Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: Mount process exited, code=exited, status=1/FAILURE Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-lxd-22662.mount: Failed with result 'exit-code'. Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit for lxd, revision 22662. journal for failed service snap-snapd-15177.mount --- -- Journal begins at Thu 2022-03-17 09:54:14 UTC, ends at Thu 2022-03-17 10:01:49 UTC. -- Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Mounting Mount unit for snapd, revision 15177... Mar 17 10:01:43 autopkgtest-lxd-oolwau mount[92]: mount: /snap/snapd/15177: mount failed: Operation not permitted. Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: Mount process exited, code=exited, status=1/FAILURE Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: snap-snapd-15177.mount: Failed with result 'exit-code'. Mar 17 10:01:43 autopkgtest-lxd-oolwau systemd[1]: Failed to mount Mount unit for snapd, revision 15177. FAIL [...] == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.HBv169/build.sBq/real-tree/debian/tests/boot-and-services", line 69, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['snap-lxd-22662.mount loaded failed fai[119 chars]177'] != [] First list contains 2 additional elements. First extra element 0: 'snap-lxd-22662.mount loaded failed failed Mount unit for lxd, revision 22662' + [] - ['snap-lxd-22662.mount loaded failed failed Mount unit for lxd, revision ' - '22662', - 'snap-snapd-15177.mount loaded failed failed Mount unit for snapd, revision ' - '15177'] This testcase started to fail with the latest re-spin of the kernels (uploaded on mar-16), however the only patch applied between the previous kernels and the current ones is a CVE fix which is unlikely to be causing this failure: "ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()" https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/impish/commit/?id=da5043b3ed2889300211ba35d5a7d2f3b9255d1b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965293/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943441] Re: lxc: lxc-test-parse-config-file failure
The issue is still reproducible in Impish (lxc 1:4.0.12-0ubuntu1~21.10.1) ** Also affects: lxc (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu Impish) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1943441 Title: lxc: lxc-test-parse-config-file failure Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Impish: Confirmed Bug description: I'm getting the following error with the lxc kernel autotest on impish: 08:46:04 DEBUG| parse_config_file.c: 60: set_get_compare_clear_save_load: expected value "system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key "lxc.selinux.context" do not match 08:46:04 DEBUG| 08:46:04 DEBUG| parse_config_file.c: 382: main: lxc.selinux.context 08:46:06 INFO | ERRORubuntu_lxc.lxc-test-parse-config-file ubuntu_lxc.lxc-test-parse-config-filetimestamp=1631090766localtime=Sep 08 08:46:06Command failed, rc=1, Command returned non-zero exit status * Command: /tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file Exit status: 1 Duration: 0.0550210475922 stderr: parse_config_file.c: 60: set_get_compare_clear_save_load: expected value "system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key "lxc.selinux.context" do not match parse_config_file.c: 382: main: lxc.selinux.context I haven't investigated very much, but it looks like a (mis)configuration change / issue. Does it ring any bell? Otherwise I'll investigate more. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1943441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966188] Re: lxc: lxc-test-parse-config-file failure on Jammy (retrieved value "" for config key "lxc.selinux.context")
I can still see the issue from bug 1943441 with impish:linux. However, with one of the s390x systems (s2lp4 which is a lpar), I only get the second error reported on this bug: STARTubuntu_lxc.lxc-test-parse-config-file ubuntu_lxc.lxc-test-parse-config-filetimestamp=1649849603timeout=1200 localtime=Apr 13 11:33:23 Persistent state client._record_indent now set to 2 Persistent state client.unexpected_reboot now set to ('ubuntu_lxc.lxc-test-parse-config-file', 'ubuntu_lxc.lxc-test-parse-config-file') Waiting for pid 62280 for 1200 seconds System python is too old, crash handling disabled Running '/tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file' [stderr] parse_config_file.c: 49: set_get_compare_clear_save_load: failed to set config item "lxc.seccomp.profile" to "/some/seccomp/file" [stderr] [stderr] parse_config_file.c: 580: main: lxc.seccomp.profile -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1966188 Title: lxc: lxc-test-parse-config-file failure on Jammy (retrieved value "" for config key "lxc.selinux.context") Status in lxc package in Ubuntu: New Bug description: After bug 1943441 fixed for Impish, we're seeing this again on Jammy, with lxc 1:4.0.12-0ubuntu2 from Jammy archive. STARTubuntu_lxc.lxc-test-parse-config-file ubuntu_lxc.lxc-test-parse-config-filetimestamp=1648013959timeout=1200 localtime=Mar 23 05:39:19 Persistent state client._record_indent now set to 2 Persistent state client.unexpected_reboot now set to ('ubuntu_lxc.lxc-test-parse-config-file', 'ubuntu_lxc.lxc-test-parse-config-file') Waiting for pid 79677 for 1200 seconds System python is too old, crash handling disabled Running '/tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file' parse_config_file.c: 63: set_get_compare_clear_save_load: expected value "system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key "lxc.selinux.context" do not match parse_config_file.c: 49: set_get_compare_clear_save_load: failed to set config item "lxc.seccomp.profile" to "/some/seccomp/file" parse_config_file.c: 580: main: lxc.seccomp.profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1966188/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958904] Re: autopkgtest is failing on jammy with "no space left on device"
** Also affects: initramfs-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu Bionic) Status: New => Triaged ** Changed in: initramfs-tools (Ubuntu Bionic) Importance: Undecided => High ** Changed in: initramfs-tools (Ubuntu Impish) Status: New => Triaged ** Changed in: initramfs-tools (Ubuntu Impish) Importance: Undecided => High ** Changed in: initramfs-tools (Ubuntu Bionic) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: initramfs-tools (Ubuntu Focal) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: initramfs-tools (Ubuntu Impish) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1958904 Title: autopkgtest is failing on jammy with "no space left on device" Status in initramfs-tools package in Ubuntu: Fix Committed Status in initramfs-tools source package in Bionic: Triaged Status in initramfs-tools source package in Focal: Triaged Status in initramfs-tools source package in Impish: Triaged Bug description: In debian/tests/prep-image we create an image file of 1GB, but recent jammy cloud images are (barely) bigger than that, for example the current one uncompressed is 1001MB... Maybe we should consider to create image files of 2GB or even bigger, considering that we are only going to allocate the space that is actually needed, because we create the file using truncate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958904] Re: autopkgtest is failing on jammy with "no space left on device"
initramgs-tools in bionic doesn't have debian/tests/. ** Changed in: initramfs-tools (Ubuntu Bionic) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1958904 Title: autopkgtest is failing on jammy with "no space left on device" Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Invalid Status in initramfs-tools source package in Focal: Triaged Status in initramfs-tools source package in Impish: Triaged Bug description: In debian/tests/prep-image we create an image file of 1GB, but recent jammy cloud images are (barely) bigger than that, for example the current one uncompressed is 1001MB... Maybe we should consider to create image files of 2GB or even bigger, considering that we are only going to allocate the space that is actually needed, because we create the file using truncate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958904] Re: autopkgtest is failing on jammy with "no space left on device"
debdiff for Impish (0.140ubuntu6.1). Compile-tested in my ppa and locally tested with autopkgtest. ** Description changed: - In debian/tests/prep-image we create an image file of 1GB, but recent - jammy cloud images are (barely) bigger than that, for example the - current one uncompressed is 1001MB... + [Impact] + In debian/tests/prep-image we create an image file of 1GB, but recent jammy cloud images are (barely) bigger than that, for example the current one uncompressed is 1001MB... Maybe we should consider to create image files of 2GB or even bigger, considering that we are only going to allocate the space that is actually needed, because we create the file using truncate. + + [Test Plan] + Run autotestpkg tests from initramfs-tools package. The "net" test is the one that depends on the image created by 'prep-image'. The testcase should complete successfully without the temporary image running out of space. + + [Where problems could occur] + The creation of a larger image for the tests could fail if the filesystem of the test system is low on disk space. However, as mentioned before, as the image file is created using 'truncate', only the necessary space needed to uncompress the cloudimg will be used on the filesystem. Apart from that, we assume that 2GB of free space should be available on every test system used for Ubuntu autopkgtest. ** Description changed: [Impact] - In debian/tests/prep-image we create an image file of 1GB, but recent jammy cloud images are (barely) bigger than that, for example the current one uncompressed is 1001MB... + In debian/tests/prep-image we create an image file of 1GB, but recent jammy/focal cloud images are (barely) bigger than that, for example the current one uncompressed is 1001MB... + + Example of a test failure: + https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/i/initramfs-tools/20220126_160323_8bcd1@/log.gz Maybe we should consider to create image files of 2GB or even bigger, considering that we are only going to allocate the space that is actually needed, because we create the file using truncate. [Test Plan] Run autotestpkg tests from initramfs-tools package. The "net" test is the one that depends on the image created by 'prep-image'. The testcase should complete successfully without the temporary image running out of space. [Where problems could occur] The creation of a larger image for the tests could fail if the filesystem of the test system is low on disk space. However, as mentioned before, as the image file is created using 'truncate', only the necessary space needed to uncompress the cloudimg will be used on the filesystem. Apart from that, we assume that 2GB of free space should be available on every test system used for Ubuntu autopkgtest. ** Patch added: "debdiff for Impish (0.140ubuntu6.1)" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+attachment/5557651/+files/initramfs-tools_0.140ubuntu6.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1958904 Title: autopkgtest is failing on jammy with "no space left on device" Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Invalid Status in initramfs-tools source package in Focal: In Progress Status in initramfs-tools source package in Impish: In Progress Bug description: [Impact] In debian/tests/prep-image we create an image file of 1GB, but recent jammy/focal cloud images are (barely) bigger than that, for example the current one uncompressed is 1001MB... Example of a test failure: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/i/initramfs-tools/20220126_160323_8bcd1@/log.gz Maybe we should consider to create image files of 2GB or even bigger, considering that we are only going to allocate the space that is actually needed, because we create the file using truncate. [Test Plan] Run autotestpkg tests from initramfs-tools package. The "net" test is the one that depends on the image created by 'prep-image'. The testcase should complete successfully without the temporary image running out of space. [Where problems could occur] The creation of a larger image for the tests could fail if the filesystem of the test system is low on disk space. However, as mentioned before, as the image file is created using 'truncate', only the necessary space needed to uncompress the cloudimg will be used on the filesystem. Apart from that, we assume that 2GB of free space should be available on every test system used for Ubuntu autopkgtest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packa
[Touch-packages] [Bug 1958904] Re: autopkgtest is failing on jammy with "no space left on device"
debdiff for Focal (0.136ubuntu6.7). Compile-tested in my ppa and locally tested with autopkgtest. ** Patch added: "debdiff for Focal (0.136ubuntu6.7)" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+attachment/5557652/+files/initramfs-tools_0.136ubuntu6.7.debdiff ** Changed in: initramfs-tools (Ubuntu Focal) Status: Triaged => In Progress ** Changed in: initramfs-tools (Ubuntu Impish) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1958904 Title: autopkgtest is failing on jammy with "no space left on device" Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Invalid Status in initramfs-tools source package in Focal: In Progress Status in initramfs-tools source package in Impish: In Progress Bug description: [Impact] In debian/tests/prep-image we create an image file of 1GB, but recent jammy/focal cloud images are (barely) bigger than that, for example the current one uncompressed is 1001MB... Example of a test failure: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/i/initramfs-tools/20220126_160323_8bcd1@/log.gz Maybe we should consider to create image files of 2GB or even bigger, considering that we are only going to allocate the space that is actually needed, because we create the file using truncate. [Test Plan] Run autotestpkg tests from initramfs-tools package. The "net" test is the one that depends on the image created by 'prep-image'. The testcase should complete successfully without the temporary image running out of space. [Where problems could occur] The creation of a larger image for the tests could fail if the filesystem of the test system is low on disk space. However, as mentioned before, as the image file is created using 'truncate', only the necessary space needed to uncompress the cloudimg will be used on the filesystem. Apart from that, we assume that 2GB of free space should be available on every test system used for Ubuntu autopkgtest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960094] Re: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal
Attached is the testcase log from the run with the previous focal:linux kernel version (5.4.0-97.110). I believe that it's very unlikely that this issue is caused by a kernel change. Between versions 5.4.0-97.110 and 5.4.0-99.112 only a few cifs patches were reverted to fix a regression (https://launchpad.net/ubuntu/+source/linux/5.4.0-99.112). These patches were applied to 5.4.0-97.110 and reverted on 5.4.0-99.112. I haven't looked at the lxc testcases, but cifs changes should unlikely cause lxc failures. ** Attachment added: "sru-generic-metal-akis.amd64-5.4.0-97.110-ubuntu_lxc-log.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960094/+attachment/5559658/+files/sru-generic-metal-akis.amd64-5.4.0-97.110-ubuntu_lxc-log.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1960094 Title: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal Status in linux package in Ubuntu: New Status in lxc package in Ubuntu: Incomplete Status in linux source package in Focal: New Status in lxc source package in Focal: Incomplete Bug description: There are failures in ubuntu_lxc regression tests on Focal/linux/5.4.0-99.112 sru cycle 2022.01.03 with the error lxc-create: symbol lookup error: lxc-create: undefined symbol: strlcat These errors did not appear on previous kernels in the same cycle and now have a few tests failing on all architectures and systems as of Feb 4th 2022 it seems. Log with details is attached in the comments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960094/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960034] Re: systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32
Confirmed that systemd storage testacase is now successful with impish:linux 5.13.0-30.33: amd64 - https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220207_183233_91879@/log.gz arm64 - https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220207_164846_df7a7@/log.gz ppc64el - https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220207_155813_b0af1@/log.gz ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1960034 Title: systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32 Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in linux source package in Impish: Fix Committed Status in systemd source package in Impish: Invalid Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux/5.13.0-29.32 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220204_114518_6b600@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220201_135548_7f169@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220201_110103_b02e4@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960034/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776381] Re: lxc-test-api-reboot will hang with autopkgtest
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1776381 Title: lxc-test-api-reboot will hang with autopkgtest Status in ubuntu-kernel-tests: Confirmed Status in lxc package in Ubuntu: New Bug description: Steps: 1. Deploy Bionic on a bare-metal system. 2. Enable deb-src, install the autopkgtest package 3. sudo autopkgtest lxc -- null Result: * The test will hang, a "reboot" lxc container will be created. The last message on the screen will be: make[1]: Entering directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' make[1]: Nothing to be done for 'all-am'. make[1]: Leaving directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' * Tried to connect to the "reboot" container with "sudo lxc-console reboot", but nothing there: Connected to tty 1 Type to exit the console, to enter Ctrl+a itself * If you kill the job and run it again, this time the test will go on (fail with the lxc-test-api-reboot test, as the container has already been created) This issue can be reproduced on an amd64 box and a s390x zKVM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1776381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1933090] Re: systemd/245.4-4ubuntu3.6 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** Also affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-5.11 (Ubuntu) Status: New => Won't Fix ** Changed in: linux-hwe-5.11 (Ubuntu Focal) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1933090 Title: systemd/245.4-4ubuntu3.6 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: Won't Fix Status in linux-hwe-5.15 package in Ubuntu: New Status in systemd package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: Won't Fix Status in linux-hwe-5.15 source package in Focal: New Status in systemd source package in Focal: New Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz In arm64, ppc64el and s390x, 'root-unittests' fails with: /* test_protect_sysctl */ Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311, function test_protect_sysctl(). A borting. sysctlseccomp terminated by signal ABRT. Assertion 'wait_for_terminate_and_check("sysctlseccomp", pid, WAIT_LOG) == EXIT_SUCCESS' failed at s rc/test/test-seccomp.c:324, function test_protect_sysctl(). Aborting. FAIL: test-seccomp (code: 134) In amd64, 'upstream' also fails on 'TEST-24-UNIT-TESTS', which apparently is caused by the same 'test-seccomp.c:311' assertion failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1933090] Re: systemd/245.4-4ubuntu3.6 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
This is still failing in Focal, now with linux-hwe-5.15: https://autopkgtest.ubuntu.com/results/autopkgtest- focal/focal/amd64/s/systemd/20221122_044608_4c928@/log.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1933090 Title: systemd/245.4-4ubuntu3.6 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: Won't Fix Status in linux-hwe-5.15 package in Ubuntu: New Status in systemd package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: Won't Fix Status in linux-hwe-5.15 source package in Focal: New Status in systemd source package in Focal: New Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz In arm64, ppc64el and s390x, 'root-unittests' fails with: /* test_protect_sysctl */ Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311, function test_protect_sysctl(). A borting. sysctlseccomp terminated by signal ABRT. Assertion 'wait_for_terminate_and_check("sysctlseccomp", pid, WAIT_LOG) == EXIT_SUCCESS' failed at s rc/test/test-seccomp.c:324, function test_protect_sysctl(). Aborting. FAIL: test-seccomp (code: 134) In amd64, 'upstream' also fails on 'TEST-24-UNIT-TESTS', which apparently is caused by the same 'test-seccomp.c:311' assertion failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
The issue with the dkms package has been fixed via bug 1915051. ** Changed in: dkms (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in apt package in Ubuntu: Invalid Status in dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
Hi Dimitri, These are the dkms packages which had the build failure fixed after the -hwe switch in Focal from 5.4 to 5.8: bcmwl=6.30.223.271+bdcom-0ubuntu7~20.04.1 nvidia-graphics-drivers-340=340.108-0ubuntu5.20.04.1 virtualbox-hwe=6.1.16-dfsg-6ubuntu1.20.04.1 And this is the list of all the other dkms packages which had to be updated to fix build failures in Focal with the 5.8 kernel: acpi-call=1.1.0-5ubuntu0.1 backport-iwlwifi-dkms=8324-0ubuntu3~20.04.2 dahdi-linux=1:2.11.1~dfsg-1ubuntu6.1 dm-writeboost=2.2.9-1ubuntu1.1 evdi=1.7.0+dfsg-1ubuntu1~20.04.2 gost-crypto=0.3.2-2ubuntu0.1 iptables-netflow=2.4-2ubuntu0.2 lime-forensics=1.9-1ubuntu0.1 lttng-modules=2.12.2-1ubuntu1~20.04.1 openafs=1.8.4~pre1-1ubuntu2.1 oss4=4.2-build2010-5ubuntu6~20.04.1 r8168=8.048.00-1ubuntu0.20.04.1 rtl8812au=4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.1 sysdig=0.26.4-1ubuntu0.2 v4l2loopback=0.12.3-1ubuntu0.3 virtualbox=6.1.16-dfsg-6~ubuntu1.20.04.1 zfs-linux=0.8.3-1ubuntu12.6 None of these updates has been released to -security, so if we want to make sure that users running the hwe-5.8 kernel from -security will not get broken dkms packages we need to release them all. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in apt package in Ubuntu: Invalid Status in dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1913189] Re: systemd 245.4-4ubuntu3.4 ADT test failure with linux-hwe-5.8 5.8.0-41.46~20.04.1
Thanks everyone for getting it fixed! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1913189 Title: systemd 245.4-4ubuntu3.4 ADT test failure with linux-hwe-5.8 5.8.0-41.46~20.04.1 Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Bug description: [impact] test-fs-util fails when running under 5.8 kernel [test case] see autopkgtest runs, e.g. amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/s/systemd/20210121_140925_39a30@/log.gz [regression potential] any regression would likely result in incorrectly passed or failed build-time or autopkgtest-time test run [scope] this is needed in f and b this was fixed upstream with commit 5b5ce6298e which was first included in v247, and has already been backported to g in bug 1891527. while it's unlikely that the 5.8 kernel will ever officially be available directly in b, this test case is also run at build time, so if the lp build farm is ever updated to the 5.8 kernel this test case would begin failing during build, so the patch should be backported there as well. this isn't needed in x as the test-fs-util test isn't present there. [original description] Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20210121_140925_39a30@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20210121_021134_f3c65@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20210121_090718_fa164@/log.gz The failing test case is: TEST-24-UNIT-TESTS: === Failed test log === --- test-fs-util begin --- /* test_chase_symlinks */ /* test_unlink_noerrno */ /* test_readlink_and_make_absolute */ /* test_var_tmp */ /* test_dot_or_dot_dot */ /* test_access_fd */ /* test_touch_file */ Assertion 'mknod(a, 0775 | S_IFBLK, makedev(0, 0)) >= 0' failed at src/test/test-fs-util.c:637, funct ion test_touch_file(). Aborting. --- test-fs-util end --- make: Leaving directory '/tmp/autopkgtest.KFUfZH/build.scn/src/test/TEST-24-UNIT-TESTS' make: *** [Makefile:4: run] Error 1 This issue has been solved in Groovy on bug 1891527, likely the fix needs to be backported to systemd in Focal for the testcase to pass with the 5.8 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1913189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905044] Re: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8
@ddstreet thanks for pointing to that other bug report. After applying the fix from https://github.com/systemd/systemd/pull/16424 to systemd_245.4-4ubuntu3.3, 'systemd show' does work: $ ./systemctl show -p CapabilityBoundingSet apparmor CapabilityBoundingSet=cap_chown cap_dac_override cap_dac_read_search cap_fowner cap_fsetid cap_kill But the testcase fails a little bit down the line: $ ./test-cap-list cap_chown = 0 cap_dac_override = 1 cap_dac_read_search = 2 [...] cap_block_suspend vs. cap_block_suspend cap_audit_read vs. cap_audit_read Assertion 'streq(t1, t)' failed at src/test/test-cap-list.c:61, function test_capability_set_one(). Aborting. Aborted (core dumped) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1905044 Title: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8 Status in systemd package in Ubuntu: Invalid Status in systemd source package in Focal: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz The failing testcases are: - root-unittests Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at src/test/test-cap-list.c:60, funct ion test_capability_set_one(). Aborting. FAIL: test-cap-list (code: 134) - upstream TEST-24-UNIT-TESTS: --- test-cap-list begin --- Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at src/test/test-cap-list.c:60, funct ion test_capability_set_one(). Aborting. --- test-cap-list end --- Both seem to be failing with the same assertion. These tests are successful on Focal with linux 5.4, therefore they would regress when upgrading the kernel from 5.4 to 5.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905044] Re: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8
So I'm wondering if some other fixes are needed as well do fix the testcase. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1905044 Title: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8 Status in systemd package in Ubuntu: Invalid Status in systemd source package in Focal: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz The failing testcases are: - root-unittests Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at src/test/test-cap-list.c:60, funct ion test_capability_set_one(). Aborting. FAIL: test-cap-list (code: 134) - upstream TEST-24-UNIT-TESTS: --- test-cap-list begin --- Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at src/test/test-cap-list.c:60, funct ion test_capability_set_one(). Aborting. --- test-cap-list end --- Both seem to be failing with the same assertion. These tests are successful on Focal with linux 5.4, therefore they would regress when upgrading the kernel from 5.4 to 5.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed
** Changed in: linux (Ubuntu Groovy) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Committed Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Committed Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1913189] [NEW] systemd 245.4-4ubuntu3.4 ADT test failure with linux-hwe-5.8 5.8.0-41.46~20.04.1
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20210121_140925_39a30@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20210121_021134_f3c65@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20210121_090718_fa164@/log.gz The failing test case is: TEST-24-UNIT-TESTS: === Failed test log === --- test-fs-util begin --- /* test_chase_symlinks */ /* test_unlink_noerrno */ /* test_readlink_and_make_absolute */ /* test_var_tmp */ /* test_dot_or_dot_dot */ /* test_access_fd */ /* test_touch_file */ Assertion 'mknod(a, 0775 | S_IFBLK, makedev(0, 0)) >= 0' failed at src/test/test-fs-util.c:637, funct ion test_touch_file(). Aborting. --- test-fs-util end --- make: Leaving directory '/tmp/autopkgtest.KFUfZH/build.scn/src/test/TEST-24-UNIT-TESTS' make: *** [Makefile:4: run] Error 1 This issue has been solved in Groovy on bug 1891527, likely the fix needs to be backported to systemd in Focal for the testcase to pass with the 5.8 kernel. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Focal) Status: New => Confirmed ** Description changed: Testing failed on: - amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20210121_140925_39a30@/log.gz - arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20210121_021134_f3c65@/log.gz - s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20210121_090718_fa164@/log.gz + amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20210121_140925_39a30@/log.gz + arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20210121_021134_f3c65@/log.gz + s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20210121_090718_fa164@/log.gz + + The failing test case is: + + TEST-24-UNIT-TESTS: + + === Failed test log === + --- test-fs-util begin --- + /* test_chase_symlinks */ + /* test_unlink_noerrno */ + /* test_readlink_and_make_absolute */ + /* test_var_tmp */ + /* test_dot_or_dot_dot */ + /* test_access_fd */ + /* test_touch_file */ + Assertion 'mknod(a, 0775 | S_IFBLK, makedev(0, 0)) >= 0' failed at src/test/test-fs-util.c:637, funct + ion test_touch_file(). Aborting. + --- test-fs-util end --- + make: Leaving directory '/tmp/autopkgtest.KFUfZH/build.scn/src/test/TEST-24-UNIT-TESTS' + make: *** [Makefile:4: run] Error 1 + + + This issue has been solved in Groovy on bug 1891527, likely the fix needs to be backported to systemd in Focal for the testcase to pass with the 5.8 kernel. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1913189 Title: systemd 245.4-4ubuntu3.4 ADT test failure with linux-hwe-5.8 5.8.0-41.46~20.04.1 Status in systemd package in Ubuntu: New Status in systemd source package in Focal: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20210121_140925_39a30@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20210121_021134_f3c65@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20210121_090718_fa164@/log.gz The failing test case is: TEST-24-UNIT-TESTS: === Failed test log === --- test-fs-util begin --- /* test_chase_symlinks */ /* test_unlink_noerrno */ /* test_readlink_and_make_absolute */ /* test_var_tmp */ /* test_dot_or_dot_dot */ /* test_access_fd */ /* test_touch_file */ Assertion 'mknod(a, 0775 | S_IFBLK, makedev(0, 0)) >= 0' failed at src/test/test-fs-util.c:637, funct ion test_touch_file(). Aborting. --- test-fs-util end --- make: Leaving directory '/tmp/autopkgtest.KFUfZH/build.scn/src/test
[Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
The false positives on kernel ADT matrix were caused by an issue in dkms-autopkgtest shipped by the dkms package, as we discussed here: https://lists.ubuntu.com/archives/kernel-team/2021-February/116985.html All the dkms packages which were failing to build in Focal with the hwe-5.8 kernel are now fixed. We need now to fix dkms to make sure this won't happen again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in apt package in Ubuntu: Invalid Status in dkms package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Committed Status in upower source package in Bionic: Incomplete Status in gnome-control-center source package in Cosmic: Fix Released Status in gnome-shell source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in upower source package in Cosmic: Fix Released Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821625] [NEW] systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)
Public bug reported: Starting with systemd 237-3ubuntu10.14, the testcase test-seccomp is failing on Bionic on ppc64el with the error messages: Operating on architecture: ppc Failed to add n/a() rule for architecture ppc, skipping: Bad address Operating on architecture: ppc64 Failed to add n/a() rule for architecture ppc64, skipping: Bad address Operating on architecture: ppc64-le Failed to add n/a() rule for architecture ppc64-le, skipping: Numerical argument out of domain Assertion 'p == MAP_FAILED' failed at ../src/test/test-seccomp.c:413, function test_memory_deny_write_execute_mmap(). Aborting. memoryseccomp-mmap terminated by signal ABRT. Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG) == EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:427, function test_memory_deny_write_execute_mmap(). Aborting. Aborted (core dumped) FAIL: test-seccomp (code: 134) Full logs at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190302_025135_d0e38@/log.gz The testcase passed with systemd version 237-3ubuntu10.13 running on the same 4.15.0-45 kernel on ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190228_154406_6b12f@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Bionic) Importance: Undecided Status: Confirmed ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Bionic) Status: New => Confirmed ** Summary changed: - systemd 237-3ubuntu10.15 ADT test failure with linux-hwe 4.18.0-17.18~18.04.1 + systemd 237-3ubuntu10.14 ADT test failure on Bionic (test-seccomp) ** Summary changed: - systemd 237-3ubuntu10.14 ADT test failure on Bionic (test-seccomp) + systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp) ** Description changed: - Testing failed on: - ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190322_025013_23073@/log.gz + Starting with systemd 237-3ubuntu10.14, the testcase test-seccomp is + failing on Bionic on ppc64el with the error messages: + + Operating on architecture: ppc + Failed to add n/a() rule for architecture ppc, skipping: Bad address + Operating on architecture: ppc64 + Failed to add n/a() rule for architecture ppc64, skipping: Bad address + Operating on architecture: ppc64-le + Failed to add n/a() rule for architecture ppc64-le, skipping: Numerical argument out of domain + Assertion 'p == MAP_FAILED' failed at ../src/test/test-seccomp.c:413, function test_memory_deny_write_execute_mmap(). Aborting. + memoryseccomp-mmap terminated by signal ABRT. + Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG) == EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:427, function test_memory_deny_write_execute_mmap(). Aborting. + Aborted (core dumped) + FAIL: test-seccomp (code: 134) + + Full logs at: + https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190302_025135_d0e38@/log.gz + + The testcase passed with systemd version 237-3ubuntu10.13 running on the same 4.15.0-45 kernel on ppc64el: + https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190228_154406_6b12f@/log.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1821625 Title: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test- seccomp) Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: Confirmed Bug description: Starting with systemd 237-3ubuntu10.14, the testcase test-seccomp is failing on Bionic on ppc64el with the error messages: Operating on architecture: ppc Failed to add n/a() rule for architecture ppc, skipping: Bad address Operating on architecture: ppc64 Failed to add n/a() rule for architecture ppc64, skipping: Bad address Operating on architecture: ppc64-le Failed to add n/a() rule for architecture ppc64-le, skipping: Numerical argument out of domain Assertion 'p == MAP_FAILED' failed at ../src/test/test-seccomp.c:413, function test_memory_deny_write_execute_mmap(). Aborting. memoryseccomp-mmap terminated by signal ABRT. Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG) == EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:427, function test_memory_deny_write_execute_mmap(). Aborting. Aborted (core dumped) FAIL: test-seccomp (code: 134) Full l
[Touch-packages] [Bug 1805834] [NEW] systemd 237-3ubuntu10.9 ADT test failure with linux-aws 4.15.0-1029.30
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/s/systemd/20181129_104127_fbcbf@/log.gz upstream:test/TEST-22-TMPFILES is a new testcases and has been failing with all 4.15 kernels (at least on Bionic). upstream:test/TEST-03-JOBS test/TEST-09-ISSUE-2691 test/TEST-19-DELEGATE have been flaky for the last releases. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Description changed: Testing failed on: - amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/s/systemd/20181129_104127_fbcbf@/log.gz + amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/s/systemd/20181129_104127_fbcbf@/log.gz + + upstream:test/TEST-22-TMPFILES is a new testcases and has been failing + with all 4.15 kernels (at least on Bionic). + + upstream:test/TEST-03-JOBS test/TEST-09-ISSUE-2691 test/TEST-19-DELEGATE + have been flaky for the last releases. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1805834 Title: systemd 237-3ubuntu10.9 ADT test failure with linux-aws 4.15.0-1029.30 Status in systemd package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/s/systemd/20181129_104127_fbcbf@/log.gz upstream:test/TEST-22-TMPFILES is a new testcases and has been failing with all 4.15 kernels (at least on Bionic). upstream:test/TEST-03-JOBS test/TEST-09-ISSUE-2691 test/TEST-19-DELEGATE have been flaky for the last releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa
** Changed in: linux (Ubuntu Bionic) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: Won't Fix Status in mesa source package in Cosmic: Fix Released Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821625] Re: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1821625 Title: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test- seccomp) Status in libseccomp package in Ubuntu: Incomplete Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Status in libseccomp source package in Bionic: Incomplete Status in linux source package in Bionic: Fix Committed Status in systemd source package in Bionic: Invalid Bug description: Starting with systemd 237-3ubuntu10.14, the testcase test-seccomp is failing on Bionic on ppc64el with the error messages: Operating on architecture: ppc Failed to add n/a() rule for architecture ppc, skipping: Bad address Operating on architecture: ppc64 Failed to add n/a() rule for architecture ppc64, skipping: Bad address Operating on architecture: ppc64-le Failed to add n/a() rule for architecture ppc64-le, skipping: Numerical argument out of domain Assertion 'p == MAP_FAILED' failed at ../src/test/test-seccomp.c:413, function test_memory_deny_write_execute_mmap(). Aborting. memoryseccomp-mmap terminated by signal ABRT. Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG) == EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:427, function test_memory_deny_write_execute_mmap(). Aborting. Aborted (core dumped) FAIL: test-seccomp (code: 134) Full logs at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190302_025135_d0e38@/log.gz The testcase passed with systemd version 237-3ubuntu10.13 running on the same 4.15.0-45 kernel on ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190228_154406_6b12f@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1821625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837235] [NEW] systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage)
Public bug reported: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/s/systemd/20190719_14_3528c@/log.gz The storage testcase is failing on i386. Running the testcase manually, it hangs at: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk testcrypt1! Looking at the storage testcase, on function start_password_agent(), it expects the 'disk scsi_debug' string on the systemd ask-password file, however the contains: Message=Please enter passphrase for disk testcrypt1! That doesn't seems to happen on other architectures. On amd64, the testcase output is: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk scsi_debug (testcrypt1)! ok [...] ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Summary changed: - systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 + systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage) ** Description changed: Testing failed on: - i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/s/systemd/20190719_14_3528c@/log.gz + i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/s/systemd/20190719_14_3528c@/log.gz + + The storage testcase is failing on i386. Running the testcase manually, + it hangs at: + + systemd-229/debian/tests$ sudo ./storage + test_luks_by_devname (__main__.CryptsetupTest) + LUKS device by plain device name, empty ... Please enter passphrase for disk testcrypt1! + + Looking at the storage testcase, on function start_password_agent(), it + expects the 'disk scsi_debug' string on the systemd ask-password file, + however the contains: + + Message=Please enter passphrase for disk testcrypt1! + + That doesn't seems to happen on other architectures. On amd64, the + testcase output is: + + systemd-229/debian/tests$ sudo ./storage + test_luks_by_devname (__main__.CryptsetupTest) + LUKS device by plain device name, empty ... Please enter passphrase for disk scsi_debug (testcrypt1)! + ok + [...] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837235 Title: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage) Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Status in linux source package in Xenial: New Status in systemd source package in Xenial: New Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/s/systemd/20190719_14_3528c@/log.gz The storage testcase is failing on i386. Running the testcase manually, it hangs at: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk testcrypt1! Looking at the storage testcase, on function start_password_agent(), it expects the 'disk scsi_debug' string on the systemd ask-password file, however the contains: Message=Please enter passphrase for disk testcrypt1! That doesn't seems to happen on other architectures. On amd64, the testcase output is: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk scsi_debug (testcrypt1)! ok [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837235] Re: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage)
systemd relies on some udev properties to craft the message that will be displayed by the cryptsetup service when a password is required. For this testcase, the scsi_debug module is loaded and the device created by it is used for the tests. With xenial kernel 4.4.0-154-generic, udevadm returns for the scsi_debug block device: $ udevadm info /dev/sdb P: /devices/pseudo_0/adapter0/host2/target2:0:0/2:0:0:0/block/sdb N: sdb S: disk/by-id/scsi-353301770 S: disk/by-id/wwn-0x53301770 E: DEVLINKS=/dev/disk/by-id/scsi-353301770 /dev/disk/by-id/wwn-0x53301770 E: DEVNAME=/dev/sdb E: DEVPATH=/devices/pseudo_0/adapter0/host2/target2:0:0/2:0:0:0/block/sdb E: DEVTYPE=disk E: ID_BUS=scsi E: ID_MODEL=scsi_debug E: ID_MODEL_ENC=scsi_debug\x20\x20\x20\x20\x20\x20 E: ID_REVISION=0184 E: ID_SCSI=1 E: ID_SCSI_SERIAL=6000 E: ID_SERIAL=353301770 E: ID_SERIAL_SHORT=53301770 E: ID_TARGET_PORT=300 E: ID_TYPE=disk E: ID_VENDOR=Linux E: ID_VENDOR_ENC=Linux\x20\x20\x20 E: ID_WWN=0x53301770 E: ID_WWN_WITH_EXTENSION=0x53301770 E: MAJOR=8 E: MINOR=16 E: SUBSYSTEM=block E: TAGS=:systemd: E: USEC_INITIALIZED=121942203 However, with kernel 4.4.0-156-generic the output is: $ udevadm info /dev/sdb P: /devices/pseudo_0/adapter0/host2/target2:0:0/2:0:0:0/block/sdb N: sdb E: DEVNAME=/dev/sdb E: DEVPATH=/devices/pseudo_0/adapter0/host2/target2:0:0/2:0:0:0/block/sdb E: DEVTYPE=disk E: MAJOR=8 E: MINOR=16 E: SUBSYSTEM=block E: TAGS=:systemd: E: USEC_INITIALIZED=36737967 systemd expects one of the following properties to be set: "ID_PART_ENTRY_NAME\0" "DM_NAME\0" "ID_MODEL_FROM_DATABASE\0" "ID_MODEL\0"; But none of them is present with the newer kernel. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837235 Title: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage) Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: In Progress Status in linux source package in Xenial: Incomplete Status in systemd source package in Xenial: In Progress Status in linux source package in Bionic: New Status in systemd source package in Bionic: In Progress Status in linux source package in Disco: New Status in systemd source package in Disco: In Progress Status in linux source package in Eoan: Incomplete Status in systemd source package in Eoan: In Progress Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/s/systemd/20190719_14_3528c@/log.gz The storage testcase is failing on i386. Running the testcase manually, it hangs at: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk testcrypt1! Looking at the storage testcase, on function start_password_agent(), it expects the 'disk scsi_debug' string on the systemd ask-password file, however the contains: Message=Please enter passphrase for disk testcrypt1! That doesn't seems to happen on other architectures. On amd64, the testcase output is: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk scsi_debug (testcrypt1)! ok [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837235] Re: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage)
** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux (Ubuntu Disco) Status: New => Invalid ** Changed in: linux (Ubuntu Eoan) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837235 Title: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage) Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in systemd source package in Xenial: In Progress Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: In Progress Status in linux source package in Disco: Invalid Status in systemd source package in Disco: In Progress Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: In Progress Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/s/systemd/20190719_14_3528c@/log.gz The storage testcase is failing on i386. Running the testcase manually, it hangs at: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk testcrypt1! Looking at the storage testcase, on function start_password_agent(), it expects the 'disk scsi_debug' string on the systemd ask-password file, however the contains: Message=Please enter passphrase for disk testcrypt1! That doesn't seems to happen on other architectures. On amd64, the testcase output is: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk scsi_debug (testcrypt1)! ok [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837235] Re: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage)
The missing properties seems to be caused by this error: $ sudo /lib/systemd/systemd-udevd --debug [...] IMPORT 'scsi_id --export --whitelisted -d /dev/sdb' /lib/udev/rules.d/60-persistent-storage.rules:44 starting 'scsi_id --export --whitelisted -d /dev/sdb' Process 'scsi_id --export --whitelisted -d /dev/sdb' failed with exit code 1. The above command was run while running 'modprobe scsi_debug' in another terminal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837235 Title: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage) Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in systemd source package in Xenial: In Progress Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: In Progress Status in linux source package in Disco: Invalid Status in systemd source package in Disco: In Progress Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: In Progress Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/s/systemd/20190719_14_3528c@/log.gz The storage testcase is failing on i386. Running the testcase manually, it hangs at: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk testcrypt1! Looking at the storage testcase, on function start_password_agent(), it expects the 'disk scsi_debug' string on the systemd ask-password file, however the contains: Message=Please enter passphrase for disk testcrypt1! That doesn't seems to happen on other architectures. On amd64, the testcase output is: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk scsi_debug (testcrypt1)! ok [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837235] Re: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage)
This is a kernel bug, introduced by one of these patches applied to xenial: commit d823dfc03906fd278ae6f48219c4ed53faee6f9d Author: Al Viro Date: Thu Jun 27 20:16:00 2019 +0200 bio_copy_from_iter(): get rid of copying iov_iter commit aceb27a7de5fc65a3fc70ccac344f33099e8a4dc Author: Keith Busch Date: Thu Jun 27 20:16:00 2019 +0200 block: Clear kernel memory before copying to user commit a713ff5b13e8fd9e331fd84232806316aa9e9b2a Author: Keith Busch Date: Thu Jun 27 20:16:00 2019 +0200 block/bio: Do not zero user pages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837235 Title: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage) Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in systemd source package in Xenial: In Progress Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: In Progress Status in linux source package in Disco: Invalid Status in systemd source package in Disco: In Progress Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: In Progress Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/s/systemd/20190719_14_3528c@/log.gz The storage testcase is failing on i386. Running the testcase manually, it hangs at: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk testcrypt1! Looking at the storage testcase, on function start_password_agent(), it expects the 'disk scsi_debug' string on the systemd ask-password file, however the contains: Message=Please enter passphrase for disk testcrypt1! That doesn't seems to happen on other architectures. On amd64, the testcase output is: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk scsi_debug (testcrypt1)! ok [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837235] Re: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage)
Those commits were applied for LP: #1834499. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837235 Title: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage) Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in systemd source package in Xenial: In Progress Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: In Progress Status in linux source package in Disco: Invalid Status in systemd source package in Disco: In Progress Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: In Progress Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/s/systemd/20190719_14_3528c@/log.gz The storage testcase is failing on i386. Running the testcase manually, it hangs at: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk testcrypt1! Looking at the storage testcase, on function start_password_agent(), it expects the 'disk scsi_debug' string on the systemd ask-password file, however the contains: Message=Please enter passphrase for disk testcrypt1! That doesn't seems to happen on other architectures. On amd64, the testcase output is: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk scsi_debug (testcrypt1)! ok [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837235] Re: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage)
How to easily reproduce the issue: $ sudo modprobe scsi_debug $ sudo /lib/udev/scsi_id --export --whitelisted -v -d /dev/sdb 8:16: ioctl failed: Invalid argument 8:16: Unable to get INQUIRY vpd 0 page 0x0. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837235 Title: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage) Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in systemd source package in Xenial: In Progress Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: In Progress Status in linux source package in Disco: Invalid Status in systemd source package in Disco: In Progress Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: In Progress Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/s/systemd/20190719_14_3528c@/log.gz The storage testcase is failing on i386. Running the testcase manually, it hangs at: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk testcrypt1! Looking at the storage testcase, on function start_password_agent(), it expects the 'disk scsi_debug' string on the systemd ask-password file, however the contains: Message=Please enter passphrase for disk testcrypt1! That doesn't seems to happen on other architectures. On amd64, the testcase output is: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk scsi_debug (testcrypt1)! ok [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: Won't Fix Status in mesa source package in Cosmic: Fix Released Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa
There's a follow up fix for bionic/linux which needs to be applied: https://lists.ubuntu.com/archives/kernel-team/2019-August/103175.html So I'm going to reset the task. ** Changed in: linux (Ubuntu Bionic) Status: Fix Released => In Progress ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: Won't Fix Status in mesa source package in Cosmic: Fix Released Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804864] Re: autopkgtest regression TEST-22-TMPFILES are not executable
This bug was supposed to be fixed on bionic with systemd (237-3ubuntu10.11) but it's still failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-bionic/bionic/amd64/s/systemd/20190118_154706_1d013@/log.gz == TEST-22-TMPFILES == make: Entering directory '/tmp/autopkgtest.wPokuU/build.7Yo/src/test/TEST-22-TMPFILES' /bin/sh: 1: ./test.sh: Permission denied make: *** [clean] Error 126 Makefile:4: recipe for target 'clean' failed make: Leaving directory '/tmp/autopkgtest.wPokuU/build.7Yo/src/test/TEST-22-TMPFILES' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1804864 Title: autopkgtest regression TEST-22-TMPFILES are not executable Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Newly added testcase in a security upload used a traditional GNU patch format, instead of using extended git patch format, as supported by GNU patch. Therefore, executable bits on shells scripts were lost, resulting in autopkgtest failures. [Test Case] * `upstream` test/TEST-22-TMPFILES autopkgtest case should pass. [Regression Potential] * This is testcode change only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804864] Re: autopkgtest regression TEST-22-TMPFILES are not executable
While running ADT tests with the new systemd packages on both Bionic and Cosmic we get the following error on the src pkg install phase: dpkg-source: warning: diff 'src/debian/patches/test-Set-executable-bits- on-TEST-22-TMPFILES-shell-script.patch' doesn't contain any patch Looking back at the log history of the tests, the testcase never failed on Cosmic. An example is this test result with systemd 239-7ubuntu9: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/amd64/s/systemd/20181013_012203_828ba@/log.gz And as I stated on my previous comment, the test is still failing on Bionic. So it seems that the fix proposed for this issue is not taking any effect. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1804864 Title: autopkgtest regression TEST-22-TMPFILES are not executable Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Newly added testcase in a security upload used a traditional GNU patch format, instead of using extended git patch format, as supported by GNU patch. Therefore, executable bits on shells scripts were lost, resulting in autopkgtest failures. [Test Case] * `upstream` test/TEST-22-TMPFILES autopkgtest case should pass. [Regression Potential] * This is testcode change only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766727] Re: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04
** Also affects: linux-hwe-edge (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-edge (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1766727 Title: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04 Status in Ubuntu on IBM z Systems: Fix Released Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-edge package in Ubuntu: Fix Committed Status in s390-tools package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in initramfs-tools source package in Xenial: Invalid Status in linux source package in Xenial: New Status in linux-hwe-edge source package in Xenial: Fix Committed Status in s390-tools source package in Xenial: Fix Released Status in ubuntu-release-upgrader source package in Xenial: Invalid Status in initramfs-tools source package in Bionic: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-hwe-edge source package in Bionic: Invalid Status in s390-tools source package in Bionic: Fix Released Status in ubuntu-release-upgrader source package in Bionic: Invalid Bug description: [Impact] Upgrades of linux-image-generic-hwe-16.04-edge will fail to configure because the post-update script for zipl will fail. [Test Case] Upgrade linux-image-generic-hwe-16.04-edge from xenial to xenial-proposed on s390x. [Regression] zipl update on s390x might fail, causing the system to be unbootable. Upgrading from 16.04 to 18.04 using 'do-release-upgrade -d' results in: Errors were encountered while processing: initramfs-tools Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). --- Processing triggers for systemd (237-3ubuntu10) ... Processing triggers for initramfs-tools (0.130ubuntu3) ... update-initramfs: Generating /boot/initrd.img-4.4.0-121-generic Using config file '/etc/zipl.conf' Error: Ramdisk file '/boot/initrd.img' in section 'ubuntu': No such file or directory run-parts: /etc/initramfs/post-update.d//zz-zipl exited with return code 1 [1mdpkg:[0m error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Processing triggers for ca-certificates (20180409) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Processing triggers for dictionaries-common (1.27.2) ... Processing triggers for linux-image-4.15.0-19-generic (4.15.0-19.20) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.15.0-19-generic Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasdb (0104). Done. /etc/kernel/postinst.d/zz-zipl: Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasdb (0104). Done. Processing triggers for sgml-base (1.29) ... Processing triggers for resolvconf (1.79ubuntu10) ... Processing triggers for ureadahead (0.100.0-20) ... Errors were encountered while processing: initramfs-tools Log ended: 2018-04-24 13:12:40 --- ApportVersion: 2.20.9-0ubuntu6 Architecture: s390x DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-19-generic s390x UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago) UserGroups: adm cdrom cpacfstats dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1766727/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766727] Re: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04
** Changed in: linux-hwe-edge (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux-hwe-edge (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1766727 Title: initramfs-tools exception during pm.DoInstall with do-release-upgrade from 16.04 to 18.04 Status in Ubuntu on IBM z Systems: Fix Released Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-edge package in Ubuntu: Fix Committed Status in s390-tools package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in initramfs-tools source package in Xenial: Invalid Status in linux source package in Xenial: New Status in linux-hwe-edge source package in Xenial: Fix Committed Status in s390-tools source package in Xenial: Fix Released Status in ubuntu-release-upgrader source package in Xenial: Invalid Status in initramfs-tools source package in Bionic: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-hwe-edge source package in Bionic: Invalid Status in s390-tools source package in Bionic: Fix Released Status in ubuntu-release-upgrader source package in Bionic: Invalid Bug description: [Impact] Upgrades of linux-image-generic-hwe-16.04-edge will fail to configure because the post-update script for zipl will fail. [Test Case] Upgrade linux-image-generic-hwe-16.04-edge from xenial to xenial-proposed on s390x. [Regression] zipl update on s390x might fail, causing the system to be unbootable. Upgrading from 16.04 to 18.04 using 'do-release-upgrade -d' results in: Errors were encountered while processing: initramfs-tools Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). --- Processing triggers for systemd (237-3ubuntu10) ... Processing triggers for initramfs-tools (0.130ubuntu3) ... update-initramfs: Generating /boot/initrd.img-4.4.0-121-generic Using config file '/etc/zipl.conf' Error: Ramdisk file '/boot/initrd.img' in section 'ubuntu': No such file or directory run-parts: /etc/initramfs/post-update.d//zz-zipl exited with return code 1 [1mdpkg:[0m error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Processing triggers for ca-certificates (20180409) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Processing triggers for dictionaries-common (1.27.2) ... Processing triggers for linux-image-4.15.0-19-generic (4.15.0-19.20) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.15.0-19-generic Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasdb (0104). Done. /etc/kernel/postinst.d/zz-zipl: Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasdb (0104). Done. Processing triggers for sgml-base (1.29) ... Processing triggers for resolvconf (1.79ubuntu10) ... Processing triggers for ureadahead (0.100.0-20) ... Errors were encountered while processing: initramfs-tools Log ended: 2018-04-24 13:12:40 --- ApportVersion: 2.20.9-0ubuntu6 Architecture: s390x DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-19-generic s390x UpgradeStatus: Upgraded to bionic on 2018-04-24 (0 days ago) UserGroups: adm cdrom cpacfstats dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1766727/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
** Changed in: linux (Ubuntu Artful) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Fix Released Status in tar package in Ubuntu: New Status in linux source package in Artful: Fix Committed Status in tar source package in Artful: New Bug description: == SRU Justification == This bug causes btrfs and tar sparse to truncate archives. This bug has been fixed in v4.15-rc3 by commit e3b8a4858566, which has a prereq commit of f48bf66b662e. These commits were cc'd to upstream stable and are already in Bionic. However, upstream 4.13 is EOL, so Artful never recieved the fixes, which is the reason for the SRU request. == Fixes == f48bf66b662e ("Btrfs: move definition of the function btrfs_find_new_delalloc_bytes") e3b8a4858566 ("Btrfs: fix reported number of inode blocks after buffered append writes") == Regression Potential == Low. This fix was also sent and accepted to stable, so it has had additional upstream review. == Test Case == A test kernel was built with these patches and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install)
[Touch-packages] [Bug 1734908] [NEW] systemd-rfkill service times out when a new rfkill device is added
Public bug reported: 1. Issue Package version: systemd=234-2ubuntu12.1 The following issue was observed while running network- manager=1.8.4-1ubuntu3 autopkgtest on Artful: --- Nov 21 17:00:32 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch Status... Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Start operation timed out. Terminating. Nov 21 17:01:02 autopkgtest systemd[1]: Failed to start Load/Save RF Kill Switch Status. Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Unit entered failed state. Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Failed with result 'timeout'. --- This happens after the testcase inserts the fake-rfkill module (a module shipped with network-manager tests that registers a new fake device with the rfkill subsystem). 2. How to reproduce 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase $ cd network-manager-1.8.4 $ sudo ./debian/tests/killswitches-no-urfkill 3. Fix The issue is fixed by the following systemd upstream patches: --- https://github.com/systemd/systemd/commit/8ec1a07998758f6a85f3ea5bf2ed14d87609398f#diff-275947967677827e2b72930d97f1b8ac commit 8ec1a07998758f6a85f3ea5bf2ed14d87609398f Author: S. Fan Date: Mon Jul 31 05:10:10 2017 -0500 rfkill: fix erroneous behavior when polling the udev monitor (#6489) Comparing udev_device_get_sysname(device) and sysname will always return true. We need to check the device received from udev monitor instead. Also, fd_wait_for_event() sometimes never exits. Better set a timeout here. --- --- https://github.com/systemd/systemd/commit/c7f6ca9379279affa8f22d15fa13063491f86a49#diff-275947967677827e2b72930d97f1b8ac commit c7f6ca9379279affa8f22d15fa13063491f86a49 Author: Xiang Fan Date: Wed Aug 9 05:51:53 2017 -0500 rfkill: fix typo (#6574) --- With the fixed, the output from systemd-rfkill is: --- Nov 28 15:27:54 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch Status... Nov 28 15:27:59 autopkgtest systemd-rfkill[14843]: Timed out waiting for udev monitor. Nov 28 15:27:59 autopkgtest systemd[1]: Started Load/Save RF Kill Switch Status. --- The patches are needed to fix the ADT tests observed with Artful tests on ppc64el architecture: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1734908 Title: systemd-rfkill service times out when a new rfkill device is added Status in systemd package in Ubuntu: New Bug description: 1. Issue Package version: systemd=234-2ubuntu12.1 The following issue was observed while running network- manager=1.8.4-1ubuntu3 autopkgtest on Artful: --- Nov 21 17:00:32 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch Status... Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Start operation timed out. Terminating. Nov 21 17:01:02 autopkgtest systemd[1]: Failed to start Load/Save RF Kill Switch Status. Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Unit entered failed state. Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Failed with result 'timeout'. --- This happens after the testcase inserts the fake-rfkill module (a module shipped with network-manager tests that registers a new fake device with the rfkill subsystem). 2. How to reproduce 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase $ cd network-manager-1.8.4 $ sudo ./debian/tests/killswitches-no-urfkill 3. Fix The issue is fixed by the following systemd upstream patches: --- https://github.com/systemd/systemd/commit/8ec1a07998758f6a85f3ea5bf2ed14d87609398f#diff-275947967677827e2b72930d97f1b8ac commit 8ec1a07998758f6a85f3ea5bf2ed14d87609398f Author: S. Fan Date: Mon Jul 31 05:10:10 2017 -0500 rfkill: fix erroneous behavior when polling the udev monitor (#6489) Comparing udev
[Touch-packages] [Bug 1734908] Re: systemd-rfkill service times out when a new rfkill device is added
** Description changed: 1. Issue + + Package version: systemd=234-2ubuntu12.1 The following issue was observed while running network- manager=1.8.4-1ubuntu3 autopkgtest on Artful: --- Nov 21 17:00:32 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch Status... Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Start operation timed out. Terminating. Nov 21 17:01:02 autopkgtest systemd[1]: Failed to start Load/Save RF Kill Switch Status. Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Unit entered failed state. Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Failed with result 'timeout'. --- This happens after the testcase inserts the fake-rfkill module (a module shipped with network-manager tests that registers a new fake device with the rfkill subsystem). 2. How to reproduce 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase $ cd network-manager-1.8.4 $ sudo ./debian/tests/killswitches-no-urfkill 3. Fix The issue is fixed by the following systemd upstream patches: --- https://github.com/systemd/systemd/commit/8ec1a07998758f6a85f3ea5bf2ed14d87609398f#diff-275947967677827e2b72930d97f1b8ac commit 8ec1a07998758f6a85f3ea5bf2ed14d87609398f Author: S. Fan Date: Mon Jul 31 05:10:10 2017 -0500 - rfkill: fix erroneous behavior when polling the udev monitor (#6489) - - Comparing udev_device_get_sysname(device) and sysname will always return - true. We need to check the device received from udev monitor instead. - - Also, fd_wait_for_event() sometimes never exits. Better set a timeout - here. + rfkill: fix erroneous behavior when polling the udev monitor (#6489) + + Comparing udev_device_get_sysname(device) and sysname will always return + true. We need to check the device received from udev monitor instead. + + Also, fd_wait_for_event() sometimes never exits. Better set a timeout + here. --- --- https://github.com/systemd/systemd/commit/c7f6ca9379279affa8f22d15fa13063491f86a49#diff-275947967677827e2b72930d97f1b8ac commit c7f6ca9379279affa8f22d15fa13063491f86a49 Author: Xiang Fan Date: Wed Aug 9 05:51:53 2017 -0500 - rfkill: fix typo (#6574) + rfkill: fix typo (#6574) --- With the fixed, the output from systemd-rfkill is: --- Nov 28 15:27:54 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch Status... Nov 28 15:27:59 autopkgtest systemd-rfkill[14843]: Timed out waiting for udev monitor. Nov 28 15:27:59 autopkgtest systemd[1]: Started Load/Save RF Kill Switch Status. --- The patches are needed to fix the ADT tests observed with Artful tests on ppc64el architecture: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1734908 Title: systemd-rfkill service times out when a new rfkill device is added Status in systemd package in Ubuntu: New Bug description: 1. Issue Package version: systemd=234-2ubuntu12.1 The following issue was observed while running network- manager=1.8.4-1ubuntu3 autopkgtest on Artful: --- Nov 21 17:00:32 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch Status... Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Start operation timed out. Terminating. Nov 21 17:01:02 autopkgtest systemd[1]: Failed to start Load/Save RF Kill Switch Status. Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Unit entered failed state. Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Failed with result 'timeout'. --- This happens after the testcase inserts the fake-rfkill module (a module shipped with network-manager tests that registers a new fake device with the rfkill subsystem). 2. How to reproduce 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase $ cd network-manager-1.8.4 $ sudo ./debian/tests/killswitches-no-urfkill 3. Fix The issue is fixed by the foll
[Touch-packages] [Bug 1734908] Re: systemd-rfkill service times out when a new rfkill device is added
This is a debdiff for Artful applicable to systemd 234-2ubuntu12.1. This was built with pbuilder and tested in an Artful VM and the fix works as expected. ** Patch added: "1-234-2ubuntu12.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734908/+attachment/5016091/+files/1-234-2ubuntu12.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1734908 Title: systemd-rfkill service times out when a new rfkill device is added Status in systemd package in Ubuntu: New Bug description: 1. Issue Package version: systemd=234-2ubuntu12.1 The following issue was observed while running network- manager=1.8.4-1ubuntu3 autopkgtest on Artful: --- Nov 21 17:00:32 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch Status... Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Start operation timed out. Terminating. Nov 21 17:01:02 autopkgtest systemd[1]: Failed to start Load/Save RF Kill Switch Status. Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Unit entered failed state. Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Failed with result 'timeout'. --- This happens after the testcase inserts the fake-rfkill module (a module shipped with network-manager tests that registers a new fake device with the rfkill subsystem). 2. How to reproduce 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase $ cd network-manager-1.8.4 $ sudo ./debian/tests/killswitches-no-urfkill 3. Fix The issue is fixed by the following systemd upstream patches: --- https://github.com/systemd/systemd/commit/8ec1a07998758f6a85f3ea5bf2ed14d87609398f#diff-275947967677827e2b72930d97f1b8ac commit 8ec1a07998758f6a85f3ea5bf2ed14d87609398f Author: S. Fan Date: Mon Jul 31 05:10:10 2017 -0500 rfkill: fix erroneous behavior when polling the udev monitor (#6489) Comparing udev_device_get_sysname(device) and sysname will always return true. We need to check the device received from udev monitor instead. Also, fd_wait_for_event() sometimes never exits. Better set a timeout here. --- --- https://github.com/systemd/systemd/commit/c7f6ca9379279affa8f22d15fa13063491f86a49#diff-275947967677827e2b72930d97f1b8ac commit c7f6ca9379279affa8f22d15fa13063491f86a49 Author: Xiang Fan Date: Wed Aug 9 05:51:53 2017 -0500 rfkill: fix typo (#6574) --- With the fixed, the output from systemd-rfkill is: --- Nov 28 15:27:54 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch Status... Nov 28 15:27:59 autopkgtest systemd-rfkill[14843]: Timed out waiting for udev monitor. Nov 28 15:27:59 autopkgtest systemd[1]: Started Load/Save RF Kill Switch Status. --- The patches are needed to fix the ADT tests observed with Artful tests on ppc64el architecture: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18
I have opened bug 1734908 for the systemd issue. ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in linux package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Status in linux source package in Artful: Triaged Status in network-manager source package in Artful: New Bug description: ppc64el ADT log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful/artful/ppc64el/n/network- manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18
This is a debdiff for Artful applicable to network-manager 1.8.4-1ubuntu3. This was built with pbuilder and the testcase shipped with the source packaged works as expected (on the environment described on this bug report only if the fix for bug 1734908 is also applied). ** Patch added: "1-1.8.4-1ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321/+attachment/5016266/+files/1-1.8.4-1ubuntu4.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in linux package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Status in linux source package in Artful: Triaged Status in network-manager source package in Artful: New Bug description: ppc64el ADT log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful/artful/ppc64el/n/network- manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734908] Re: systemd-rfkill service times out when a new rfkill device is added
** Description changed: - 1. Issue - - Package version: systemd=234-2ubuntu12.1 + [Impact] The following issue was observed while running network- - manager=1.8.4-1ubuntu3 autopkgtest on Artful: + manager=1.8.4-1ubuntu3 autopkgtest on Artful with + systemd=234-2ubuntu12.1: --- Nov 21 17:00:32 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch Status... Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Start operation timed out. Terminating. Nov 21 17:01:02 autopkgtest systemd[1]: Failed to start Load/Save RF Kill Switch Status. Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Unit entered failed state. Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Failed with result 'timeout'. --- This happens after the testcase inserts the fake-rfkill module (a module shipped with network-manager tests that registers a new fake device with the rfkill subsystem). - 2. How to reproduce + On Artful, it causes the network-manager autopkgtest killswitches-no- + urfkill to fail (see bug 1733321). - 2.1. Download network-manager package source code - $ apt-get source network-manager - 2.2. Run killswitches-no-urfkill testcase - $ cd network-manager-1.8.4 - $ sudo ./debian/tests/killswitches-no-urfkill - - 3. Fix + [Fix] The issue is fixed by the following systemd upstream patches: --- https://github.com/systemd/systemd/commit/8ec1a07998758f6a85f3ea5bf2ed14d87609398f#diff-275947967677827e2b72930d97f1b8ac commit 8ec1a07998758f6a85f3ea5bf2ed14d87609398f Author: S. Fan Date: Mon Jul 31 05:10:10 2017 -0500 rfkill: fix erroneous behavior when polling the udev monitor (#6489) Comparing udev_device_get_sysname(device) and sysname will always return true. We need to check the device received from udev monitor instead. Also, fd_wait_for_event() sometimes never exits. Better set a timeout here. --- --- https://github.com/systemd/systemd/commit/c7f6ca9379279affa8f22d15fa13063491f86a49#diff-275947967677827e2b72930d97f1b8ac commit c7f6ca9379279affa8f22d15fa13063491f86a49 Author: Xiang Fan Date: Wed Aug 9 05:51:53 2017 -0500 rfkill: fix typo (#6574) --- - With the fixed, the output from systemd-rfkill is: + With the fixes, the output from systemd-rfkill is: --- Nov 28 15:27:54 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch Status... Nov 28 15:27:59 autopkgtest systemd-rfkill[14843]: Timed out waiting for udev monitor. Nov 28 15:27:59 autopkgtest systemd[1]: Started Load/Save RF Kill Switch Status. --- The patches are needed to fix the ADT tests observed with Artful tests on ppc64el architecture: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz + + + [Test Case] + + 2.1. Download network-manager package source code + $ apt-get source network-manager + + 2.2. Run killswitches-no-urfkill testcase + $ cd network-manager-1.8.4 + $ sudo ./debian/tests/killswitches-no-urfkill + + + [Regression Potential] + + Regression potential is minimal, since the fix has been applied some + months ago on upstream github repo and it's being shipped with systemd + on Bionic (systemd=235-3ubuntu2) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1734908 Title: systemd-rfkill service times out when a new rfkill device is added Status in systemd package in Ubuntu: In Progress Bug description: [Impact] The following issue was observed while running network- manager=1.8.4-1ubuntu3 autopkgtest on Artful with systemd=234-2ubuntu12.1: --- Nov 21 17:00:32 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch Status... Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Start operation timed out. Terminating. Nov 21 17:01:02 autopkgtest systemd[1]: Failed to start Load/Save RF Kill Switch Status. Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Unit entered failed state. Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Failed with result 'timeout'. --- This happens after the testcase inserts the fake-rfkill module (a module shipped with network-manager tests
[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18
** Description changed: - ppc64el ADT log: + [Impact] + + The killswitches-no-urfkill autopkgtest fails sometimes because nmcli + reports the old state when it's called right after rfkill block/unblock. + Adding a sleep before calling nmcli fixes the issue. + + ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful/artful/ppc64el/n/network- manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' - AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o - CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o - Building modules, stage 2. - MODPOST 1 modules - CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o - LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko + AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o + CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o + Building modules, stage 2. + MODPOST 1 modules + CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o + LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 + + + [Test Case] + + 2.1. Download network-manager package source code + $ apt-get source network-manager + + 2.2. Run killswitches-no-urfkill testcase + $ cd network-manager-1.8.4 + $ sudo ./debian/tests/killswitches-no-urfkill + + + [Regression Potential] + + No regression potential. The fix touches only the testcase shipped with + the source package and it doesn't change the binary package. The sleep + time added is very small, so no possibility of causing testcase timeout. + + + [Other Info] + + On ppc64el architecture, it was observed that a fix for systemd is also + needed (see bug 1734908) for the testcase to be successful. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in linux package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Status in linux source package in Artful: Triaged Status in network-manager source package in Artful: New Bug description: [Impact] The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. Adding a sleep before calling nmcli fixes the issue. ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful/artful/ppc64el/n/network- manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 [Test Case] 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase $ cd network-manager-1.8.4 $ sudo ./debian/tests/killswitches-no-urfkill [Regression Pot
[Touch-packages] [Bug 1734908] Re: systemd-rfkill service times out when a new rfkill device is added
Yes, this has already been fixed in Bionic. The fix was applied upstream on systemd v235, so it's shipped with systemd=235-3ubuntu2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1734908 Title: systemd-rfkill service times out when a new rfkill device is added Status in systemd package in Ubuntu: In Progress Bug description: [Impact] The following issue was observed while running network- manager=1.8.4-1ubuntu3 autopkgtest on Artful with systemd=234-2ubuntu12.1: --- Nov 21 17:00:32 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch Status... Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Start operation timed out. Terminating. Nov 21 17:01:02 autopkgtest systemd[1]: Failed to start Load/Save RF Kill Switch Status. Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Unit entered failed state. Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Failed with result 'timeout'. --- This happens after the testcase inserts the fake-rfkill module (a module shipped with network-manager tests that registers a new fake device with the rfkill subsystem). On Artful, it causes the network-manager autopkgtest killswitches-no- urfkill to fail (see bug 1733321). [Fix] The issue is fixed by the following systemd upstream patches: --- https://github.com/systemd/systemd/commit/8ec1a07998758f6a85f3ea5bf2ed14d87609398f#diff-275947967677827e2b72930d97f1b8ac commit 8ec1a07998758f6a85f3ea5bf2ed14d87609398f Author: S. Fan Date: Mon Jul 31 05:10:10 2017 -0500 rfkill: fix erroneous behavior when polling the udev monitor (#6489) Comparing udev_device_get_sysname(device) and sysname will always return true. We need to check the device received from udev monitor instead. Also, fd_wait_for_event() sometimes never exits. Better set a timeout here. --- --- https://github.com/systemd/systemd/commit/c7f6ca9379279affa8f22d15fa13063491f86a49#diff-275947967677827e2b72930d97f1b8ac commit c7f6ca9379279affa8f22d15fa13063491f86a49 Author: Xiang Fan Date: Wed Aug 9 05:51:53 2017 -0500 rfkill: fix typo (#6574) --- With the fixes, the output from systemd-rfkill is: --- Nov 28 15:27:54 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch Status... Nov 28 15:27:59 autopkgtest systemd-rfkill[14843]: Timed out waiting for udev monitor. Nov 28 15:27:59 autopkgtest systemd[1]: Started Load/Save RF Kill Switch Status. --- The patches are needed to fix the ADT tests observed with Artful tests on ppc64el architecture: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz [Test Case] 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase $ cd network-manager-1.8.4 $ sudo ./debian/tests/killswitches-no-urfkill [Regression Potential] Regression potential is minimal, since the fix has been applied some months ago on upstream github repo and it's being shipped with systemd on Bionic (systemd=235-3ubuntu2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18
Although we haven't seen the failure in Bionic yet, it might be a good idea to apply the fix on Bionic as well, which as of now has the same package version as Artful. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in linux package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Status in linux source package in Artful: Triaged Status in network-manager source package in Artful: New Bug description: [Impact] The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. Adding a sleep before calling nmcli fixes the issue. ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful/artful/ppc64el/n/network- manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 [Test Case] 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase $ cd network-manager-1.8.4 $ sudo ./debian/tests/killswitches-no-urfkill [Regression Potential] No regression potential. The fix touches only the testcase shipped with the source package and it doesn't change the binary package. The sleep time added is very small, so no possibility of causing testcase timeout. [Other Info] On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734908] Re: systemd-rfkill service times out when a new rfkill device is added
Confirmed that systemd=234-2ubuntu12.2 fixes the issue. --- Dec 5 17:14:44 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch Status... Dec 5 17:14:49 autopkgtest systemd-rfkill[7400]: Timed out waiting for udev monitor. Dec 5 17:14:49 autopkgtest systemd[1]: Started Load/Save RF Kill Switch Status. --- Thanks! ** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1734908 Title: systemd-rfkill service times out when a new rfkill device is added Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Artful: Fix Committed Bug description: [Impact] The following issue was observed while running network- manager=1.8.4-1ubuntu3 autopkgtest on Artful with systemd=234-2ubuntu12.1: --- Nov 21 17:00:32 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch Status... Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Start operation timed out. Terminating. Nov 21 17:01:02 autopkgtest systemd[1]: Failed to start Load/Save RF Kill Switch Status. Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Unit entered failed state. Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Failed with result 'timeout'. --- This happens after the testcase inserts the fake-rfkill module (a module shipped with network-manager tests that registers a new fake device with the rfkill subsystem). On Artful, it causes the network-manager autopkgtest killswitches-no- urfkill to fail (see bug 1733321). [Fix] The issue is fixed by the following systemd upstream patches: --- https://github.com/systemd/systemd/commit/8ec1a07998758f6a85f3ea5bf2ed14d87609398f#diff-275947967677827e2b72930d97f1b8ac commit 8ec1a07998758f6a85f3ea5bf2ed14d87609398f Author: S. Fan Date: Mon Jul 31 05:10:10 2017 -0500 rfkill: fix erroneous behavior when polling the udev monitor (#6489) Comparing udev_device_get_sysname(device) and sysname will always return true. We need to check the device received from udev monitor instead. Also, fd_wait_for_event() sometimes never exits. Better set a timeout here. --- --- https://github.com/systemd/systemd/commit/c7f6ca9379279affa8f22d15fa13063491f86a49#diff-275947967677827e2b72930d97f1b8ac commit c7f6ca9379279affa8f22d15fa13063491f86a49 Author: Xiang Fan Date: Wed Aug 9 05:51:53 2017 -0500 rfkill: fix typo (#6574) --- With the fixes, the output from systemd-rfkill is: --- Nov 28 15:27:54 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch Status... Nov 28 15:27:59 autopkgtest systemd-rfkill[14843]: Timed out waiting for udev monitor. Nov 28 15:27:59 autopkgtest systemd[1]: Started Load/Save RF Kill Switch Status. --- The patches are needed to fix the ADT tests observed with Artful tests on ppc64el architecture: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz [Test Case] 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase $ cd network-manager-1.8.4 $ sudo ./debian/tests/killswitches-no-urfkill [Regression Potential] Regression potential is minimal, since the fix has been applied some months ago on upstream github repo and it's being shipped with systemd on Bionic (systemd=235-3ubuntu2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734908] Re: systemd-rfkill service times out when a new rfkill device is added
I have extended the bug description to include the additional information requested by @racb. ** Description changed: [Impact] The following issue was observed while running network- manager=1.8.4-1ubuntu3 autopkgtest on Artful with systemd=234-2ubuntu12.1: --- Nov 21 17:00:32 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch Status... Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Start operation timed out. Terminating. Nov 21 17:01:02 autopkgtest systemd[1]: Failed to start Load/Save RF Kill Switch Status. Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Unit entered failed state. Nov 21 17:01:02 autopkgtest systemd[1]: systemd-rfkill.service: Failed with result 'timeout'. --- This happens after the testcase inserts the fake-rfkill module (a module shipped with network-manager tests that registers a new fake device with the rfkill subsystem). On Artful, it causes the network-manager autopkgtest killswitches-no- - urfkill to fail (see bug 1733321). - + urfkill to fail (see bug 1733321). The testcase reveals that when + running network-manager cli to query the status of a WiFi interface + ('nmcli radio wifi') it can report the wrong state of the device after + 'rfkill block/unblock' is run to change the device 'Soft blocked' state. + This can affect the state of the device presented to the user. [Fix] The issue is fixed by the following systemd upstream patches: --- https://github.com/systemd/systemd/commit/8ec1a07998758f6a85f3ea5bf2ed14d87609398f#diff-275947967677827e2b72930d97f1b8ac commit 8ec1a07998758f6a85f3ea5bf2ed14d87609398f Author: S. Fan Date: Mon Jul 31 05:10:10 2017 -0500 rfkill: fix erroneous behavior when polling the udev monitor (#6489) Comparing udev_device_get_sysname(device) and sysname will always return true. We need to check the device received from udev monitor instead. Also, fd_wait_for_event() sometimes never exits. Better set a timeout here. --- --- https://github.com/systemd/systemd/commit/c7f6ca9379279affa8f22d15fa13063491f86a49#diff-275947967677827e2b72930d97f1b8ac commit c7f6ca9379279affa8f22d15fa13063491f86a49 Author: Xiang Fan Date: Wed Aug 9 05:51:53 2017 -0500 rfkill: fix typo (#6574) --- With the fixes, the output from systemd-rfkill is: --- Nov 28 15:27:54 autopkgtest systemd[1]: Starting Load/Save RF Kill Switch Status... Nov 28 15:27:59 autopkgtest systemd-rfkill[14843]: Timed out waiting for udev monitor. Nov 28 15:27:59 autopkgtest systemd[1]: Started Load/Save RF Kill Switch Status. --- The patches are needed to fix the ADT tests observed with Artful tests on ppc64el architecture: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz - [Test Case] 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase $ cd network-manager-1.8.4 $ sudo ./debian/tests/killswitches-no-urfkill - [Regression Potential] - Regression potential is minimal, since the fix has been applied some - months ago on upstream github repo and it's being shipped with systemd - on Bionic (systemd=235-3ubuntu2) + Most of the network-manager and rfkill functionalities that can be + affected by this change are tested by killswitches-no-urfkill testcase. + It covers querying the WiFi device state using nmcli and the following + rfkill commands: list, block and unblock. These have been verified to be + either fixed or not having regressions. + + The only rfkill command that is not covered by the testcase is 'event', + which listens to rfkill events and display them. I have run tests + manually and verified that it's not affected by these changes. These are + the outputs from the unpatched and patched systemd versions while + running the killswitches-no-urfkill testcase, which adds the rfkill + device, blocks and unbloks it and removes the device (the idx value is + expected to be different): + + systemd 234-2ubuntu12.1: + --- + $ sudo rfkill event + 1513163787.877080: idx 3 type 1 op 0 soft 0 hard 0 + 1513163818.118695: idx 3 type 1 op 2 soft 1 hard 0 + 1513163818.222639: idx 3 type 1 op 2 soft 0 hard 0 + 1513163818.254778: idx 3 type 1 op 1 soft 0 hard 0 +
[Touch-packages] [Bug 1750784] Re: lxc 1.0.10-0ubuntu1.1 ADT test failure with linux-lts-xenial 4.4.0-116.140~14.04.1
Testcase fails with several network timeouts: == FAIL: lxc-tests: /usr/bin/lxc-test-autostart --- Setting up the GPG keyring ERROR: Unable to fetch GPG key from keyserver. lxc_container: lxccontainer.c: create_run_template: 1092 container creation template for lxc-test-auto failed lxc_container: lxc_create.c: main: 274 Error creating container lxc-test-auto FAIL --- == == failed to get https://cloud-images.ubuntu.com/query/trusty/server/daily-dl.current.txt There is no download available for release=trusty, stream=daily, arch=ppc64el lxc_container: lxccontainer.c: create_run_template: 1092 container creation template for 82ab30c7-13ae-4502-882e-d67e779b524a failed lxc_container: lxc_create.c: main: 274 Error creating container 82ab30c7-13ae-4502-882e-d67e779b524a Failed creating ubuntu-cloud container == This is probably a proxy configuration issue on the test node. (same as bug 1750778) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1750784 Title: lxc 1.0.10-0ubuntu1.1 ADT test failure with linux-lts-xenial 4.4.0-116.140~14.04.1 Status in lxc package in Ubuntu: New Bug description: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/ppc64el/l/lxc/20180221_030606_7df34@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1750784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750784] [NEW] lxc 1.0.10-0ubuntu1.1 ADT test failure with linux-lts-xenial 4.4.0-116.140~14.04.1
Public bug reported: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/ppc64el/l/lxc/20180221_030606_7df34@/log.gz ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1750784 Title: lxc 1.0.10-0ubuntu1.1 ADT test failure with linux-lts-xenial 4.4.0-116.140~14.04.1 Status in lxc package in Ubuntu: New Bug description: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/ppc64el/l/lxc/20180221_030606_7df34@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1750784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1755466] [NEW] network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.13.0-37.42
Public bug reported: Testing failed on: arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/arm64/n/network-manager/20180312_130751_a8f2d@/log.gz ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1755466 Title: network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.13.0-37.42 Status in network-manager package in Ubuntu: New Bug description: Testing failed on: arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/arm64/n/network-manager/20180312_130751_a8f2d@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1755466/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1755466] Re: network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.13.0-37.42
Testcase 'nm' fails with the following error: [...] [1520858777.1546] disown NMNetns singleton (0xaaab00c6a980) [1520858777.1555] disown NMLinuxPlatform singleton (0xaaab00c8b0e0) [1520858777.1566] disown NMConfig singleton (0xaaab00c74010) -- test_open_b_ip4 (__main__.ColdplugWifi) Open network, 802.11b, IPv4 ... ok test_open_b_ip6_dhcp (__main__.ColdplugWifi) Open network, 802.11b, IPv6 with DHCP, preferring temp address ... ok test_open_b_ip6_raonly_no_pe (__main__.ColdplugWifi) Open network, 802.11b, IPv6 with only RA, PE disabled ... ok test_open_b_ip6_raonly_pubaddr (__main__.ColdplugWifi) Open network, 802.11b, IPv6 with only RA, preferring public address ... ok test_open_b_ip6_raonly_tmpaddr (__main__.ColdplugWifi) Open network, 802.11b, IPv6 with only RA, preferring temp address ... ok test_open_g_ip4 (__main__.ColdplugWifi) Open network, 802.11g, IPv4 ... ok test_rfkill (__main__.ColdplugWifi) shut down connection on killswitch, restore it on unblock ... ok test_wpa1_ip4 (__main__.ColdplugWifi) WPA1, 802.11g, IPv4 ... ok test_wpa2_ip4 (__main__.ColdplugWifi) WPA2, 802.11g, IPv4 ... ok test_wpa2_ip6 (__main__.ColdplugWifi) WPA2, 802.11g, IPv6 with only RA ... ok test_auto_detect_ap (__main__.Hotplug) new AP is being detected automatically within 30s ... expected failure test_auto_detect_eth (__main__.Hotplug) new eth router is being detected automatically within 30s ... RTNETLINK answers: File exists /tmp/autopkgtest.0FzbS3/build.GsE/src/debian/tests/nm:23: PyGIWarning: NetworkManager was imported without specifying a version first. Use gi.require_version('NetworkManager', '1.0') before import to ensure that the right version gets loaded. from gi.repository import NetworkManager, NMClient, GLib /tmp/autopkgtest.0FzbS3/build.GsE/src/debian/tests/nm:23: PyGIWarning: NMClient was imported without specifying a version first. Use gi.require_version('NMClient', '1.0') before import to ensure that the right version gets loaded. from gi.repository import NetworkManager, NMClient, GLib expected failure == FAIL: test_no_ap (__main__.ColdplugWifi) no available access point -- Traceback (most recent call last): File "/tmp/autopkgtest.0FzbS3/build.GsE/src/debian/tests/network_test_base.py", line 359, in wrapped args[0].wrap_process(fn, *args, **kwargs) File "/tmp/autopkgtest.0FzbS3/build.GsE/src/debian/tests/network_test_base.py", line 263, in wrap_process self.fail(f.read()) AssertionError: Traceback (most recent call last): File "/tmp/autopkgtest.0FzbS3/build.GsE/src/debian/tests/network_test_base.py", line 252, in wrap_process fn(*args, **kwargs) File "/tmp/autopkgtest.0FzbS3/build.GsE/src/debian/tests/nm", line 406, in test_no_ap self.assertTrue(self.nmdev_w.props.managed) File "/usr/lib/python3.6/unittest/case.py", line 682, in assertTrue raise self.failureException(msg) AssertionError: False is not true -- Ran 19 tests in 360.943s FAILED (failures=1, expected failures=2) autopkgtest [12:50:41]: test nm: ---] autopkgtest [12:50:41]: test nm: - - - - - - - - - - results - - - - - - - - - - nm FAIL non-zero exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1755466 Title: network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.13.0-37.42 Status in network-manager package in Ubuntu: New Bug description: Testing failed on: arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/arm64/n/network-manager/20180312_130751_a8f2d@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1755466/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1783138 Title: hinic interfaces aren't getting predictable names Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in systemd source package in Bionic: Invalid Bug description: [Impact] Interfaces associated with Huawei "hinic" PCI adapters will not be assigned predictable names[*] and instead remain using the kernel names (e.g. eth0). This can lead to races where the interface names are not the same on every boot. For example, in a system with both 2-port hinic and 2-port igb devices, the hinic interfaces would be eth0 & eth1 if the kernel finished probing hinic before igb loaded. But if igb completes loading first, the hinic interfaces would be eth2 & eth3. [*] https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ [Test Case] grep ^eth /proc/net/dev [Fix] There's an upstream fix that properly associates the hinic interfaces with their PCI devices, providing udev with the info it needs to generate a predictable name. [Regression Risk] The big regression risk here is with existing bionic installs w/ hinic devices. They will be currently using "eth" names by default, and this change will cause those names to change to "enP" names after upgrade. However, in only certain configs are those "eth" names reliable (e.g. only NIC in the system is a hinic plug-in card). It sucks to introduce such a change in a stable release - but users will be bitten by this when they upgrade or transition to the HWE kernel anyway if we don't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1762385 Title: dell_wmi: Unknown key codes Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: New Status in linux source package in Bionic: Fix Committed Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Bogus keycode messages produced by the kernel / user annoyance * rfkill keyboard shortcuts not working as intended on some Dell machines [Test Case] * check that there are no spurious kernel messages about unknown keys in journalctl upon RFKill key presses * check that RFKill key presses work correctly and kill/restore RF capabilities [Regression Potential] * The change is scoped to particular SKUs and thus should only affect them * It is related to matching gsd support, which is in-place on xenial and up [Solution] Cherrypick upstream commit https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f [Original Bug report] RFKill key produces these messages in kernel log: dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed This key code is a notification and should be added as KEY_IGNORE here: https://github.com/torvalds/linux/blob/master/drivers/platform/x86 /dell-wmi.c#L263 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmig 2737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 18:09:03 2018 InstallationDate: Installed on 2018-03-27 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1762385/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches
** Changed in: linux (Ubuntu Xenial) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1780227 Title: locking sockets broken due to missing AppArmor socket mediation patches Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Triaged Status in apparmor source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Status in apparmor source package in Bionic: Invalid Status in linux source package in Bionic: Fix Committed Bug description: Hey, Newer systemd makes use of locks placed on AF_UNIX sockets created with the socketpair() syscall to synchronize various bits and pieces when isolating services. On kernels prior to 4.18 that do not have backported the AppArmor socket mediation patchset this will cause the locks to be denied with EACCESS. This causes systemd to be broken in LXC and LXD containers that do not run unconfined which is a pretty big deal. We have seen various bug reports related to this. See for example [1] and [2]. If feasible it would be excellent if we could backport the socket mediation patchset to all LTS kernels. Afaict, this should be 4.4 and 4.15. This will unbreak a whole range of use-cases. The socket mediation patchset is available here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4 [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779 [2]: https://github.com/systemd/systemd/issues/9493 Thanks! Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1780227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 696435] Re: wait-for-root fails to detect nbd root
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/696435 Title: wait-for-root fails to detect nbd root Status in linux package in Ubuntu: Fix Released Status in nbd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in systemd source package in Xenial: Confirmed Bug description: [Impact] Kernel does not generate any events when ndb-client connects /dev/nbd0 devices, therefore it is impossible to monitor/react to the state of /dev/nbd0. [Fix] Generate change uevent when size of /dev/nbd0 changes [Testcase] * Start udevadm monitor * modprobe nbd * use ndb-client to connect something to /dev/nbd0 * observe that there are change udev events generated on /dev/nbd0 itself [Regression Potential] There is no change to existing uevents, or their ordering. There is now an addition change event which will cause systemd to mark ndb devices as ready and trigger appropriate actions [Original Bug Report] When using an nbd root, wait-for-root blocks for 30 seconds before booting continues successfully. Using Ubuntu Natty, related packages versions: nbd-client 1:2.9.16-6ubuntu1 initramfs-tools 0.98.1ubuntu9 The wait-for-root call from /usr/share/initramfs-tools/scripts/local: while [ -z "${FSTYPE}" ]; do FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30}) # Run failure hooks, hoping one of them can fix up the system # and we can restart the wait loop. If they all fail, abort # and move on to the panic handler and shell. if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then break fi done I replaced wait-for-root with a sh script that did `set >&2`, here are the relevant environment variables at the time wait-for-root was called: ROOT='/dev/nbd0' ROOTDELAY='' ROOTFLAGS='' ROOTFSTYPE='' nbdroot='192.168.0.1,2011' It's probably worth noting that "nbd0: unknown partition table" was displayed asynchronously 1-2 seconds after wait-for-root was invoked and while it was still waiting. But I tried adding a "sleep 5" as the last line of local-top/nbd, so that the nbd message was displayed a lot before wait-for-root was called, and it didn't make a difference. So I don't think a race condition is involved in this problem. Temporarily I'm passing rootdelay=1 in the kernel command line to work around the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/696435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1731467 Title: Cannot pair BLE remote devices when using combo BT SoC Status in bluez package in Ubuntu: In Progress Status in linux package in Ubuntu: New Bug description: It has been observed that sometimes it is not possible to pair with BLE remote devices when the host system is using combo (WiFi + BT) chip. The root cause of the disconnection has been identified as coming from the internal to bluez timeout. If bluez does not hear any reply from for two seconds the link is automagically disconnected. The reason fro the silence is not however a failure of the remote device but quite often a delay in the WiFi/BT combo driver that causes the packages not to reach the bluez stack. [Impact] Not possible to pair BLE remote devices such as sensors and such with Ubuntu when the host system uses BT+WiFi combo SoC. The connection attempt is disturbed with a timeout. [Fix] It has been fixed by increasing the timeout value from 2 seconds to 4 seconds. It is enough for the events to reach the stack (measured that it takes between 3 and 3.5 seconds). [Testcase] Tested with the device that failed to connect to Ubuntu Core gateway. It fails w/o the patch, it connects just fine with the patch applied. [Regression Potential] Very small. The increased timeout is taken into consideration only for new and scan report triggered connections. It will not make any already working device to fail to pair. [Other Info] The bug has been discussed and fixed here: https://marc.info/?l=linux-bluetooth&m=150824844606937&w=2 [Patch] https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth- next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571 The patch has been accepted by the upstream and will be a part of the next kernel release. Currently in the bluetooth-next tree. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1567597 Title: implement 'complain mode' in seccomp for developer mode with snaps Status in Snappy: In Progress Status in libseccomp package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in libseccomp source package in Xenial: In Progress Status in linux source package in Xenial: Fix Committed Status in libseccomp source package in Zesty: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: A requirement for snappy is that a snap may be placed in developer mode which will put the security sandbox in complain mode such that violations against policy are logged, but permitted. In this manner learning tools can be written to parse the logs, etc and make developing on snappy easier. Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while we can set complain mode to permit all calls, they are not logged at this time. I've discussed this with upstream and we are working together on the approach. This may require a kernel patch and an update to libseccomp, to filing this bug for now as a placeholder and we'll add other tasks as necessary. UPDATE: ubuntu-core-launcher now supports the '@complain' directive that is a synonym for '@unrestricted' so people can at least turn on developer mode and not be blocked by seccomp. Proper complain mode for seccomp needs to still be implemented (this bug). [Impact] Snapd needs a way to log seccomp actions without blocking any syscalls in order to have a more useful complain mode. Such functionality has been acked upstream and patches are on their way into the Linux 4.14 kernel (backported to 4.12.0-13.14 in artful). The corresponding libseccomp changes are still undergoing review (https://github.com/seccomp/libseccomp/pull/92). The pull request adds a number of new symbols and probably isn't appropriate to backport until upstream has acked the pull request. However, only a small part of that larger pull request is needed by snapd and that change can be safely backported since the only added symbol, the SCMP_ACT_LOG macro, must match the SECCOMP_RET_LOG macro that has already been approved and merged in the upstream Linux kernel. [libseccomp Test Case] A large number of tests are ran as part of the libseccomp build. However, the "live" tests which test libseccomp with actual kernel enforcement are not ran at that time. They can be manually exercised to help catch any regressions. Note that on Artful, there's an existing test failure (20-live-basic_die%%002-1): $ sudo apt build-dep -y libseccomp $ sudo apt install -y cython $ apt source libseccomp $ cd libseccomp-* $ autoreconf -ivf && ./configure --enable-python && make check-build $ (cd tests && ./regression -T live) All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, you'll see one pre-existing failure: ... Test 20-live-basic_die%%002-1 result: FAILURE 20-live-basic_die TRAP rc=159 ... Regression Test Summary tests run: 12 tests skipped: 0 tests passed: 11 tests failed: 1 tests errored: 0 Now we can build and run a small test program to test the SCMP_ACT_LOG action in the way that snapd wants to use it for developer mode: $ sudo apt install -y libseccomp-dev $ gcc -o lp1567597-test lp1567597-test.c -lseccomp $ ./lp1567597-test With a kernel that contains the logging patches and an updated libseccomp, the exit code should be 0 and you should have an entry in the system log that looks like this: audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000 ses=2 pid=18451 comm="lp1567597-test" exe="/home/tyhicks/lp1567597-test" sig=0 arch=c03e syscall=2 compat=0 ip=0x7f547352c5c0 code=0x7ffc If you have an updated libseccomp with an old kernel, you'll see that seccomp_init() fails due to the added compatibility check inside of libseccomp determines that the kernel doesn't have proper support for the new log action: $ ./lp1567597-t
[Touch-packages] [Bug 1673350] Re: dm-queue-length module is not included in installer/initramfs
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed- yakkety'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1673350 Title: dm-queue-length module is not included in installer/initramfs Status in hw-detect package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in multipath-tools package in Ubuntu: Fix Released Status in hw-detect source package in Xenial: In Progress Status in initramfs-tools source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Status in multipath-tools source package in Xenial: Fix Committed Status in hw-detect source package in Yakkety: In Progress Status in initramfs-tools source package in Yakkety: Invalid Status in linux source package in Yakkety: Fix Committed Status in multipath-tools source package in Yakkety: Fix Committed Bug description: [Impact] Multipath users using EMC XtremIO storage as boot device or at install time may run into this issue. With the module unavailable the device is more often than not unavailable. Any users changing path selector to 'queue-length' with other storage devices may also be affected. [Test case] 1) Install on multipath system using EMC XtremIO storage / OR: a) Start d-i install on qemu with multipath enabled b) exit to d-i menu c) modify /etc/multipath.conf to define path selector as 'queue-length' for the local qemu device. d) restart multipathd if necessary. 2) Try to complete the install, setting up storage as multipath and using the multipath device as boot disk. 3) Reboot to disk. In a success case, the install should complete successfully without requiring manual configuration from the user to support the multipath storage past the normal detection of multipath and partitioning. In a failure case, the install may not complete, or rebooting may fail or lead to a system booted on a single path of the multipath device (ie. / on /dev/sda2 rather than /dev/mpatha2). [Regression Potential] The inclusion of a new multipath path selector driver should not cause any regressions, but any failure to detect, configure or boot on multipath devices following this change on XtremIO hardware or otherwise would constitute a regression potentially caused by this change. --- ---Problem Description--- dm-queue-length module is not included in installer/initramfs On Ubuntu, multipath devices using the 'queue-length' path selector are non-functional on both the installer and initramfs environments; because the 'dm-queue-length' kernel module is not included in them. The multipath-modules.udeb (src:linux) does not include it in the installer, nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs. One example is the EMC XtremIO storage, which has 'queue-length' defined as its path selector in the default multipath configuration, at least on 16.04. Other products may be affected if they are manually configured to use that path selector (e.g., via /etc/multipath.conf), and the mere switch of that might render the system _unbootable_ if booting from multipath, since the initramfs is affected. More recently this and another storage changed default path selectors out of 'queue-length', however, it's virtually possible for any storage system to be affected, with the described manual configuration change. So, this change is also desired on for the next stable release, 17.04, and later. Patches are provided for 16.04 and 17.04. Error logs in LP comment #6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1673350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1673350] Re: dm-queue-length module is not included in installer/initramfs
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1673350 Title: dm-queue-length module is not included in installer/initramfs Status in hw-detect package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in multipath-tools package in Ubuntu: Fix Released Status in hw-detect source package in Xenial: In Progress Status in initramfs-tools source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Status in multipath-tools source package in Xenial: Fix Committed Status in hw-detect source package in Yakkety: In Progress Status in initramfs-tools source package in Yakkety: Invalid Status in linux source package in Yakkety: Fix Committed Status in multipath-tools source package in Yakkety: Fix Committed Bug description: [Impact] Multipath users using EMC XtremIO storage as boot device or at install time may run into this issue. With the module unavailable the device is more often than not unavailable. Any users changing path selector to 'queue-length' with other storage devices may also be affected. [Test case] 1) Install on multipath system using EMC XtremIO storage / OR: a) Start d-i install on qemu with multipath enabled b) exit to d-i menu c) modify /etc/multipath.conf to define path selector as 'queue-length' for the local qemu device. d) restart multipathd if necessary. 2) Try to complete the install, setting up storage as multipath and using the multipath device as boot disk. 3) Reboot to disk. In a success case, the install should complete successfully without requiring manual configuration from the user to support the multipath storage past the normal detection of multipath and partitioning. In a failure case, the install may not complete, or rebooting may fail or lead to a system booted on a single path of the multipath device (ie. / on /dev/sda2 rather than /dev/mpatha2). [Regression Potential] The inclusion of a new multipath path selector driver should not cause any regressions, but any failure to detect, configure or boot on multipath devices following this change on XtremIO hardware or otherwise would constitute a regression potentially caused by this change. --- ---Problem Description--- dm-queue-length module is not included in installer/initramfs On Ubuntu, multipath devices using the 'queue-length' path selector are non-functional on both the installer and initramfs environments; because the 'dm-queue-length' kernel module is not included in them. The multipath-modules.udeb (src:linux) does not include it in the installer, nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs. One example is the EMC XtremIO storage, which has 'queue-length' defined as its path selector in the default multipath configuration, at least on 16.04. Other products may be affected if they are manually configured to use that path selector (e.g., via /etc/multipath.conf), and the mere switch of that might render the system _unbootable_ if booting from multipath, since the initramfs is affected. More recently this and another storage changed default path selectors out of 'queue-length', however, it's virtually possible for any storage system to be affected, with the described manual configuration change. So, this change is also desired on for the next stable release, 17.04, and later. Patches are provided for 16.04 and 17.04. Error logs in LP comment #6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1673350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824812] Re: apparmor does not start in Disco LXD containers
** Also affects: libvirt (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** No longer affects: libvirt (Ubuntu Disco) ** No longer affects: apparmor (Ubuntu Disco) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1824812 Title: apparmor does not start in Disco LXD containers Status in AppArmor: Triaged Status in apparmor package in Ubuntu: Fix Released Status in libvirt package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: New Bug description: In LXD apparmor now skips starting. Steps to reproduce: 1. start LXD container $ lxc launch ubuntu-daily:d d-testapparmor (disco to trigger the issue, cosmic as reference) 2. check the default profiles loaded $ aa-status => This will in cosmic and up to recently disco list plenty of profiles active even in the default install. Cosmic: 25 profiles are loaded. 25 profiles are in enforce mode. Disco: 15 profiles are loaded. 15 profiles are in enforce mode. All those 15 remaining are from snaps. The service of apparmor.service actually states that it refuses to start. $ systemctl status apparmor ... Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor in container I can get those profiles (the default installed ones) loaded, for example: $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient makes it appear 22 profiles are in enforce mode. /sbin/dhclient I was wondering as in my case I found my guest with no (=0) profiles loaded. But as shown above after "apparmor_parser -r" and package install profiles seemed fine. Then the puzzle was solved, on package install they will call apparmor_parser via the dh_apparmor snippet and it is fine. To fully disable all of them: $ lxc stop $ lxc start $ lxc exec d-testapparmor aa-status apparmor module is loaded. 0 profiles are loaded. 0 profiles are in enforce mode. 0 profiles are in complain mode. 0 processes have profiles defined. 0 processes are in enforce mode. 0 processes are in complain mode. 0 processes are unconfined but have a profile defined. That would match the service doing an early exit as shown in systemctl status output above. The package install or manual load works, but none are loaded by the service automatically e.g. on container restart. --- --- --- This bug started as: Migrations to Disco trigger "Unable to find security driver for model apparmor" This most likely is related to my KVM-in-LXD setup but it worked fine for years and I'd like to sort out what broke. I have migrated to Disco's qemu 3.1 already which makes me doubts generic issues in qemu 3.1 in general. The virt tests that run cross release work fine starting from X/B/C but all those chains fail at mirgating to Disco now with: $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live kvmguest-bionic-normal qemu+ssh://10.21.151.207/system error: unsupported configuration: Unable to find security driver for model apparmor I need to analyze what changed To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1824812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824812] Re: apparmor does not start in Disco LXD containers
** Changed in: linux (Ubuntu Disco) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1824812 Title: apparmor does not start in Disco LXD containers Status in AppArmor: Triaged Status in apparmor package in Ubuntu: Fix Released Status in libvirt package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: Fix Committed Bug description: In LXD apparmor now skips starting. Steps to reproduce: 1. start LXD container $ lxc launch ubuntu-daily:d d-testapparmor (disco to trigger the issue, cosmic as reference) 2. check the default profiles loaded $ aa-status => This will in cosmic and up to recently disco list plenty of profiles active even in the default install. Cosmic: 25 profiles are loaded. 25 profiles are in enforce mode. Disco: 15 profiles are loaded. 15 profiles are in enforce mode. All those 15 remaining are from snaps. The service of apparmor.service actually states that it refuses to start. $ systemctl status apparmor ... Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor in container I can get those profiles (the default installed ones) loaded, for example: $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient makes it appear 22 profiles are in enforce mode. /sbin/dhclient I was wondering as in my case I found my guest with no (=0) profiles loaded. But as shown above after "apparmor_parser -r" and package install profiles seemed fine. Then the puzzle was solved, on package install they will call apparmor_parser via the dh_apparmor snippet and it is fine. To fully disable all of them: $ lxc stop $ lxc start $ lxc exec d-testapparmor aa-status apparmor module is loaded. 0 profiles are loaded. 0 profiles are in enforce mode. 0 profiles are in complain mode. 0 processes have profiles defined. 0 processes are in enforce mode. 0 processes are in complain mode. 0 processes are unconfined but have a profile defined. That would match the service doing an early exit as shown in systemctl status output above. The package install or manual load works, but none are loaded by the service automatically e.g. on container restart. --- --- --- This bug started as: Migrations to Disco trigger "Unable to find security driver for model apparmor" This most likely is related to my KVM-in-LXD setup but it worked fine for years and I'd like to sort out what broke. I have migrated to Disco's qemu 3.1 already which makes me doubts generic issues in qemu 3.1 in general. The virt tests that run cross release work fine starting from X/B/C but all those chains fail at mirgating to Disco now with: $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live kvmguest-bionic-normal qemu+ssh://10.21.151.207/system error: unsupported configuration: Unable to find security driver for model apparmor I need to analyze what changed To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1824812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824864] Re: CONFIG_LOG_BUF_SHIFT set to 14 is too low on arm64
** Changed in: linux (Ubuntu Disco) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1824864 Title: CONFIG_LOG_BUF_SHIFT set to 14 is too low on arm64 Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in linux source package in Xenial: Confirmed Status in systemd source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in systemd source package in Bionic: New Status in linux source package in Cosmic: Confirmed Status in systemd source package in Cosmic: New Status in linux source package in Disco: Fix Committed Status in systemd source package in Disco: New Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: New Bug description: [Impact] * Too small dmsg kernel buf ring size leads to loosing/missing early boot kernel messages which happen before journald starts slurping them up and storing them on disc. This results in messages similar to this one on boot "missed NN kernel messages on boot". This is especially pronounced on arm64 as the default setting there is way lower than any other 32bit or 64bit architecture we ship. Also amd64 appears to have the highest setting of 18 among all architectures we ship. The best course of action to bump all 64bit arches to 18, and keep all 32bit arches at the current & upstream default of 17. [Test Case] * $ cat /boot/config-`uname -r` | grep CONFIG_LOG_BUF_SHIFT on 64bit arches result should be: CONFIG_LOG_BUF_SHIFT=18 on 32bit arches result should be: CONFIG_LOG_BUF_SHIFT=17 * run systemd adt test, the boot-and-services test case should not fail journald tests with "missed kernel messages" visible in the error logs. [Regression Potential] * Increasing the size of the log_buf, will increase kernel memory usage which cannot be reclaimed. It will now become 256kb on arm64, ppc64el, s390x instead of 8kB/128kb/128kb respectively. 32bit arches remain unchanged at 128kb. [Other Info] * Original bug report CONFIG_LOG_BUF_SHIFT policy<{ 'amd64' : '18', 'arm64' : '14', 'armhf' : '17', 'i386' : '17', 'ppc64el': '17', 's390x' : '17'}> Please set CONFIG_LOG_BUF_SHIFT to at least 17 on arm64. Potentially bump all 64-bit arches to 18 (or higher!) as was done on amd64, meaning set 18 on arm64 s390x ppc64el. I have a systemd autopkgtest test that asserts that we see Linux kernel command line in the dmesg (journalctl -k -b). And it is consistently failing on arm64 scalingstack KVM EFI machines with messages of "missing 81 kernel messages". config LOG_BUF_SHIFT int "Kernel log buffer size (16 => 64KB, 17 => 128KB)" range 12 25 default 17 depends on PRINTK help Select the minimal kernel log buffer size as a power of 2. The final size is affected by LOG_CPU_MAX_BUF_SHIFT config parameter, see below. Any higher size also might be forced by "log_buf_len" boot parameter. Examples: 17 => 128 KB 16 => 64 KB 15 => 32 KB 14 => 16 KB 13 => 8 KB 12 => 4 KB 14 sounds like redictiously low for arm64. given that 17 is default across 32-bit arches, and 18 is default on amd64. On a related note, we have CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT policy<{'amd64': '13', 'arm64': '13', 'armhf': '13', 'i386': '13', 'ppc64el': '13', 's390x': '13'}> I'm not sure if we want to bump these up to LOG_BUF_SHIFT size or not. Please backport this to xenial and up. === systemd === systemd, boot-and-services test case can bump the ring buffer before running the tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1886790] [NEW] lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with 5.4 kernels in Bionic
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz The failing test seems to be: FAIL: lxc-tests: lxc-test-device-add-remove (0s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... --- This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note that this testcase is successful on Focal with the same kernel version. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Affects: lxc (Ubuntu Bionic) Importance: High Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Description changed: Testing failed on: - amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz - arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz - ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz - s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz + amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz + arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz + ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz + s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz + + The failing test seems to be: + + FAIL: lxc-tests: lxc-test-device-add-remove (0s) + --- + Adding /dev/network_latency to the container (device_add_remove_test) failed... + --- ** Also affects: lxc (Ubuntu Bionic) Importance: Undecided Status: New ** Summary changed: - lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with linux-hwe-5.4 5.4.0-41.45~18.04.1 + lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with 5.4 kernels in Bionic ** Description changed: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz The failing test seems to be: FAIL: lxc-tests: lxc-test-device-add-remove (0s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... --- + + This is a regression from the 4.15/5.3 to 5.4 kernels. Note that this + testcase is successful on Focal with the same kernel version. ** Description changed: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz The failing test seems to be: FAIL: lxc-tests: lxc-test-de
[Touch-packages] [Bug 1884318] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with 5.4 kernels in Bionic
*** This bug is a duplicate of bug 1886790 *** https://bugs.launchpad.net/bugs/1886790 Hi Kelsey, sorry I haven't noticed you already opened this bug against the lxc issue and opened another one (bug 1886790). As I have already provided the new bug to the lxc team to look at, I'll mark this one as a duplicate. Thanks! ** This bug has been marked a duplicate of bug 1886790 lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with 5.4 kernels in Bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1884318 Title: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with 5.4 kernels in Bionic Status in lxc package in Ubuntu: Invalid Status in lxc source package in Bionic: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200617_163718_07690@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200617_165305_fce64@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1884318/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with 5.4 kernels in Bionic
This is a testcase issue, so I'm lowering the importance to 'Medium'. ** Changed in: lxc (Ubuntu Bionic) Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1886790 Title: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with 5.4 kernels in Bionic Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Bionic: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz The failing test seems to be: FAIL: lxc-tests: lxc-test-device-add-remove (0s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... --- This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note that this testcase is successful on Focal with the same kernel version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1886790/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1892130] Re: systemd 245.4-4ubuntu3.2 ADT test failure with linux-aws 5.4.0-1022.22
** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Focal) Status: New => Confirmed ** Description changed: Testing failed on: - amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20200817_235646_79e19@/log.gz + amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20200817_235646_79e19@/log.gz + + The testcase systemd-fsckd is falling with several kernels in Focal: + + == + FAIL: test_fsck_with_failure (__main__.FsckdTest) + Ensure that a failing fsck doesn't prevent fsckd to stop + -- + Traceback (most recent call last): + File "/tmp/autopkgtest.wrZrJf/build.LgN/src/debian/tests/systemd-fsckd", line 100, in test_fsck_wi + th_failure + self.assertFalse(self.is_failed_unit('process-killer')) + AssertionError: True is not false + + + == + FAIL: test_systemd_fsck_with_failure (__main__.FsckdTest) + Ensure that a failing systemd-fsck doesn't prevent fsckd to stop + -- + Traceback (most recent call last): + File "/tmp/autopkgtest.wrZrJf/build.LgN/src/debian/tests/systemd-fsckd", line 114, in test_systemd_fsck_with_failure + self.assertProcessKilled() + File "/tmp/autopkgtest.wrZrJf/build.LgN/src/debian/tests/systemd-fsckd", line 204, in assertProcessKilled + self.assertFalse(self.is_failed_unit('process-killer')) + AssertionError: True is not false -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1892130 Title: systemd 245.4-4ubuntu3.2 ADT test failure with linux-aws 5.4.0-1022.22 Status in systemd package in Ubuntu: New Status in systemd source package in Focal: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20200817_235646_79e19@/log.gz The testcase systemd-fsckd is falling with several kernels in Focal: == FAIL: test_fsck_with_failure (__main__.FsckdTest) Ensure that a failing fsck doesn't prevent fsckd to stop -- Traceback (most recent call last): File "/tmp/autopkgtest.wrZrJf/build.LgN/src/debian/tests/systemd-fsckd", line 100, in test_fsck_wi th_failure self.assertFalse(self.is_failed_unit('process-killer')) AssertionError: True is not false == FAIL: test_systemd_fsck_with_failure (__main__.FsckdTest) Ensure that a failing systemd-fsck doesn't prevent fsckd to stop -- Traceback (most recent call last): File "/tmp/autopkgtest.wrZrJf/build.LgN/src/debian/tests/systemd-fsckd", line 114, in test_systemd_fsck_with_failure self.assertProcessKilled() File "/tmp/autopkgtest.wrZrJf/build.LgN/src/debian/tests/systemd-fsckd", line 204, in assertProcessKilled self.assertFalse(self.is_failed_unit('process-killer')) AssertionError: True is not false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892130/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1892130] Re: systemd 245.4-4ubuntu3.2 ADT test failure with linux-aws 5.4.0-1022.22
This is also affecting Bionic. ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1892130 Title: systemd 245.4-4ubuntu3.2 ADT test failure with linux-aws 5.4.0-1022.22 Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: Confirmed Status in systemd source package in Focal: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20200817_235646_79e19@/log.gz The testcase systemd-fsckd is falling with several kernels in Focal: == FAIL: test_fsck_with_failure (__main__.FsckdTest) Ensure that a failing fsck doesn't prevent fsckd to stop -- Traceback (most recent call last): File "/tmp/autopkgtest.wrZrJf/build.LgN/src/debian/tests/systemd-fsckd", line 100, in test_fsck_wi th_failure self.assertFalse(self.is_failed_unit('process-killer')) AssertionError: True is not false == FAIL: test_systemd_fsck_with_failure (__main__.FsckdTest) Ensure that a failing systemd-fsck doesn't prevent fsckd to stop -- Traceback (most recent call last): File "/tmp/autopkgtest.wrZrJf/build.LgN/src/debian/tests/systemd-fsckd", line 114, in test_systemd_fsck_with_failure self.assertProcessKilled() File "/tmp/autopkgtest.wrZrJf/build.LgN/src/debian/tests/systemd-fsckd", line 204, in assertProcessKilled self.assertFalse(self.is_failed_unit('process-killer')) AssertionError: True is not false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892130/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1892130] Re: systemd 245.4-4ubuntu3.2 ADT test failure with linux-aws 5.4.0-1022.22
This issue seems to be the same as reported on bug 1892358. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1892130 Title: systemd 245.4-4ubuntu3.2 ADT test failure with linux-aws 5.4.0-1022.22 Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: Confirmed Status in systemd source package in Focal: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20200817_235646_79e19@/log.gz The testcase systemd-fsckd is falling with several kernels in Focal: == FAIL: test_fsck_with_failure (__main__.FsckdTest) Ensure that a failing fsck doesn't prevent fsckd to stop -- Traceback (most recent call last): File "/tmp/autopkgtest.wrZrJf/build.LgN/src/debian/tests/systemd-fsckd", line 100, in test_fsck_wi th_failure self.assertFalse(self.is_failed_unit('process-killer')) AssertionError: True is not false == FAIL: test_systemd_fsck_with_failure (__main__.FsckdTest) Ensure that a failing systemd-fsck doesn't prevent fsckd to stop -- Traceback (most recent call last): File "/tmp/autopkgtest.wrZrJf/build.LgN/src/debian/tests/systemd-fsckd", line 114, in test_systemd_fsck_with_failure self.assertProcessKilled() File "/tmp/autopkgtest.wrZrJf/build.LgN/src/debian/tests/systemd-fsckd", line 204, in assertProcessKilled self.assertFalse(self.is_failed_unit('process-killer')) AssertionError: True is not false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892130/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
This seems to be also affecting Bionic: http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/amd64 We did upload new kernels, so it's difficult to isolate the issue to systemd, but the failures are similar to what we are seeing in Focal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in build-essential source package in Focal: Confirmed Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: New Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had the discussion in the past, but I think I need to again bring up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until they are on reasonable success rates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packag
[Touch-packages] [Bug 1905044] [NEW] systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: Invalid ** Affects: systemd (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Summary changed: - systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8 5.8.0-30.32~20.04.1 + systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8 ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Focal) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1905044 Title: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8 Status in systemd package in Ubuntu: Invalid Status in systemd source package in Focal: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905044] Re: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8
** Description changed: Testing failed on: - amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz - arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz - ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz - s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz + amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz + arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz + ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz + s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz + + The failing testcases are: + + - root-unittests + + Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at src/test/test-cap-list.c:60, funct + ion test_capability_set_one(). Aborting. + FAIL: test-cap-list (code: 134) + + - upstream + + TEST-24-UNIT-TESTS: + + --- test-cap-list begin --- + Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at src/test/test-cap-list.c:60, funct + ion test_capability_set_one(). Aborting. + --- test-cap-list end --- + + Both seem to be failing with the same assertion. + + These tests are successful on Focal with linux 5.4, therefore they would + regress when upgrading the kernel from 5.4 to 5.8. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1905044 Title: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8 Status in systemd package in Ubuntu: Invalid Status in systemd source package in Focal: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20201117_174614_4ece6@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/s/systemd/20201117_221555_48b91@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/s/systemd/20201117_175806_e779f@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/s/systemd/20201117_153051_90e7e@/log.gz The failing testcases are: - root-unittests Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at src/test/test-cap-list.c:60, funct ion test_capability_set_one(). Aborting. FAIL: test-cap-list (code: 134) - upstream TEST-24-UNIT-TESTS: --- test-cap-list begin --- Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at src/test/test-cap-list.c:60, funct ion test_capability_set_one(). Aborting. --- test-cap-list end --- Both seem to be failing with the same assertion. These tests are successful on Focal with linux 5.4, therefore they would regress when upgrading the kernel from 5.4 to 5.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869368] Re: ubuntu_qrt_apparmor fails on ADT bionic/linux i386
** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Also affects: qa-regression-testing Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1869368 Title: ubuntu_qrt_apparmor fails on ADT bionic/linux i386 Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in apparmor source package in Bionic: New Status in linux source package in Bionic: Confirmed Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/l/linux/20200326_224620_0dd01@/log.gz Kernel version: bionic/linux 4.15.0-94.95 The ubuntu_qrt_apparmor.test-apparmor.py fails intermittently on bionic/linux i386 ADT tests. It has failed some releases in the past and I'm seeing the failure in the current release as well. I have not seen this failure on other architectures. These are the last messages on the test log: 20:12:39 ERROR| [stderr] Test mediation of file based SOCK_STREAM connect ... ok 20:12:39 ERROR| [stderr] test_libapparmor_testsuite (__main__.ApparmorTestsuites) 20:14:18 DEBUG| [stdout] unconfined_user can access confined_user's file 20:14:18 DEBUG| [stdout] unconfined_user can access default_user's file 20:14:18 DEBUG| [stdout] unconfined_user can access unconfined_group's file 20:14:18 DEBUG| [stdout] 20:15:42 ERROR| [stderr] Run libapparmor testsuite ... (Applying patch 0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying patch 0001-usr-merge-fixups.patch) ok 20:15:42 ERROR| [stderr] test_libapparmor_testsuite3 (__main__.ApparmorTestsuites) 20:15:52 DEBUG| [stdout] preparing apparmor_2.12-4ubuntu5.1.dsc... done 20:15:52 DEBUG| [stdout] 20:17:10 ERROR| [stderr] Run libapparmor testsuite (with python3) ... (Applying patch 0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying patch 0001-usr-merge-fixups.patch) ok 20:17:10 ERROR| [stderr] test_old_trusty_parser_testsuite (__main__.ApparmorTestsuites) 20:17:10 DEBUG| [stdout] preparing apparmor_2.12-4ubuntu5.1.dsc... done 20:17:10 ERROR| [stderr] Run parser regression tests from 14.04's apparmor_2.8.95~2430-0ubuntu5.3 ... (skipped: This test is only for 14.04 systems with the apparmor 2.10.95 SRU or newer installed) ok 20:17:10 ERROR| [stderr] test_old_trusty_regression_testsuite (__main__.ApparmorTestsuites) 20:17:10 ERROR| [stderr] Run kernel regression tests from 14.04's apparmor_2.8.95~2430-0ubuntu5.3 ... (skipped: This test is only for 14.04 systems with the apparmor 2.10.95 SRU or newer installed) ok 20:17:10 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites) 20:17:19 DEBUG| [stdout] 20:52:35 ERROR| [stderr] Run parser regression tests ... (Applying patch 0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying patch 0001-usr-merge-fixups.patch) ok 20:52:35 ERROR| [stderr] test_regression_testsuite (__main__.ApparmorTestsuites) 20:52:42 DEBUG| [stdout] preparing apparmor_2.12-4ubuntu5.1.dsc... done 20:52:42 DEBUG| [stdout] 21:01:56 INFO | ERROR ubuntu_qrt_apparmor.test-apparmor.py ubuntu_qrt_apparmor.test-apparmor.pytimestamp=1585256516localtime=Mar 26 21:01:56 Test subprocess failed rc=9 To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1869368/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp