[Touch-packages] [Bug 2009859] Re: systemd: networkd-test.py fails with newer kinetic kernels
I have hit this bug in the ADT testing part of the linux-aws 5.19.0-1027.28 release: https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/s/systemd/20230525_124201_d6c4e@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/arm64/s/systemd/20230525_134055_652ab@/log.gz ** Tags added: sru-20230515 -- 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/2009859 Title: systemd: networkd-test.py fails with newer kinetic kernels Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux source package in Kinetic: Confirmed Status in systemd source package in Kinetic: New Bug description: systemd autopkgtests are failing in kinetic, and they are not considered regressions. The failing test is one within networkd- test.py: == ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 680, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.10/subprocess.py", line 420, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.10/subprocess.py", line 524, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. -- Ran 35 tests in 161.770s FAILED (errors=1, skipped=2) The failures started without any changes to the systemd package, i.e. it was caused by another package upload. In particular, the failures started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine with linux 5.19.0-21.21, i.e. the version in kinetic-release. This can be demonstrated locally with autopkgtest: $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin- packages=kinetic=src:linux --setup-commands 'apt update' -- qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img Note in the above command I did not pass -U, so no packages in the test bed are upgraded. But, with: $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U -- qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic- amd64.img the kernel is upgraded, and the test fails. This can also be done manually by grabbing the systemd source on a kinetic machine (e.g. pull-lp-source systemd kinetic), and running: $ sudo python3 test/networkd-test.py DnsmasqClientTest.test_resolved_domain_restricted_dns The attached journal.txt shows systemd-resolved logs from when the test is run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 9 11:56 seq crw-rw 1 root audio 116, 33 Mar 9 11:56 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 console=ttyS0 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.16.0-debian-1.16.0-4 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU
[Touch-packages] [Bug 1848587] Re: lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2
** Description changed: + [ Impact ] + + * Test suite fails due to inexistent device (/dev/network_latency). + + [ Test Plan ] + + * Run the test suite. + * The test should pass. + + [ Where problems could occur ] + + * The regression risk is very low, and the changes only affect the + tests, so the regression scope is minimal. + + [ Other Info ] + + Original bug report: + Testing failed on: - amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/l/lxc/20191016_150939_0f81d@/log.gz - arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/arm64/l/lxc/20191016_152027_0f81d@/log.gz - ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/ppc64el/l/lxc/20191016_150251_0f81d@/log.gz - s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/s390x/l/lxc/20191016_150201_0f81d@/log.gz + amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/l/lxc/20191016_150939_0f81d@/log.gz + arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/arm64/l/lxc/20191016_152027_0f81d@/log.gz + ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/ppc64el/l/lxc/20191016_150251_0f81d@/log.gz + s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/s390x/l/lxc/20191016_150201_0f81d@/log.gz -- 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/1848587 Title: lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2 Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Bionic: Fix Committed Bug description: [ Impact ] * Test suite fails due to inexistent device (/dev/network_latency). [ Test Plan ] * Run the test suite. * The test should pass. [ Where problems could occur ] * The regression risk is very low, and the changes only affect the tests, so the regression scope is minimal. [ Other Info ] Original bug report: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/l/lxc/20191016_150939_0f81d@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/arm64/l/lxc/20191016_152027_0f81d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/ppc64el/l/lxc/20191016_150251_0f81d@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/s390x/l/lxc/20191016_150201_0f81d@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587/+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 B/5.4 kernels (device_add_remove_test)
** Description changed: + [ Impact ] + + * The device_add_remove_test test fails on the affected series (e.g. Bionic). + * Having the test fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for this test. + + [ Test Plan ] + + * Run the affected test on an affected series (e.g. Bionic). + * The test should pass. + + [ Other Info ] + + Upstream drop of network_latency: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c3082a674f46fe49383b157882c41dfabaa37113 + Related to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587 + 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. ** Description changed: [ Impact ] - * The device_add_remove_test test fails on the affected series (e.g. Bionic). - * Having the test fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for this test. + * The device_add_remove_test test fails on the affected series (e.g. Bionic). + * Having the test fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for this test. [ Test Plan ] - * Run the affected test on an affected series (e.g. Bionic). - * The test should pass. + * Run the affected test on an affected series (e.g. Bionic). + * The test should pass. [ Other Info ] Upstream drop of network_latency: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c3082a674f46fe49383b157882c41dfabaa37113 Related to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587 + + Original bug report: 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. ** Description changed: [ Impact ] * The device_add_remove_test test fails on the affected series (e.g. Bionic). * Having the test fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for this test. [ Test Plan ] * Run the affected test on an affected series (e.g. Bionic). * The test should pass. + + [ Where problems could occur ] + + * The regression risk is very low, and the changes only affect the + tests, so the regression scope is minimal. [ Other Info ] Upstream drop of network_latency: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c3082a674f46fe49383b157882c41dfabaa37113 Related to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587 Original bug report: 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:
[Touch-packages] [Bug 1939537] Re: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases
** Description changed: [ Impact ] - * The following tests fail as they try to use inexistent LXC images: -* lxc-test-apparmor-mount - * lxc-test-autostart - * lxc-test-unpriv - * lxc-test-usernic + * The following tests fail as they try to use inexistent LXC images: + * lxc-test-apparmor-mount + * lxc-test-autostart + * lxc-test-unpriv + * lxc-test-usernic - * Having them fixed for the affected series (for example Bionic) will allow us to run the LXC test suite without maintaining local changes. - + * Having them fixed for the affected series (for example, Bionic) will + allow us to run the LXC test suite without maintaining local changes for + these tests. [ Test Plan ] - * Run the affected tests on an affected series (e.g. Bionic). + * Run the affected tests on an affected series (e.g. Bionic). [ Where problems could occur ] - * The regression risk is very low and the changes only affect the tests + * The regression risk is very low and the changes only affect the tests so the regression scope is minimal. [Other info] Original bug report: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. ** Description changed: [ Impact ] * The following tests fail as they try to use inexistent LXC images: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic * Having them fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for these tests. [ Test Plan ] * Run the affected tests on an affected series (e.g. Bionic). + * The tests should pass. [ Where problems could occur ] * The regression risk is very low and the changes only affect the tests so the regression scope is minimal. [Other info] Original bug report: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. -- 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/1939537 Title: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Confirmed Status in lxc source package in Bionic: Fix Committed Bug description: [ Impact ] * The following tests fail as they try to use inexistent LXC images: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic * Having them fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for these tests. [ Test Plan ] * Run the affected tests on an affected series (e.g. Bionic). * The tests should pass. [ Where problems could occur ] * The regression risk is very low and the changes only affect the tests so the regression scope is minimal. [Other info] Original bug report: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. To manage notifications about this bug go to:
[Touch-packages] [Bug 1939537] Re: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases
** Description changed: + [ Impact ] + + * The following tests fail as they try to use inexistent LXC images: +* lxc-test-apparmor-mount + * lxc-test-autostart + * lxc-test-unpriv + * lxc-test-usernic + + * Having them fixed for the affected series (for example Bionic) will allow us to run the LXC test suite without maintaining local changes. + + + [ Test Plan ] + + * Run the affected tests on an affected series (e.g. Bionic). + + [ Where problems could occur ] + + * The regression risk is very low and the changes only affect the tests + so the regression scope is minimal. + + [Other info] + + Original bug report: + Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: - * lxc-test-apparmor-mount - * lxc-test-autostart - * lxc-test-unpriv - * lxc-test-usernic + * lxc-test-apparmor-mount + * lxc-test-autostart + * lxc-test-unpriv + * lxc-test-usernic Are now failing with: - ERROR: Couldn't find a matching image. - + ERROR: Couldn't find a matching image. + This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: - ubuntu-distro-info --supported + ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. -- 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/1939537 Title: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Confirmed Status in lxc source package in Bionic: Fix Committed Bug description: [ Impact ] * The following tests fail as they try to use inexistent LXC images: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic * Having them fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for these tests. [ Test Plan ] * Run the affected tests on an affected series (e.g. Bionic). [ Where problems could occur ] * The regression risk is very low and the changes only affect the tests so the regression scope is minimal. [Other info] Original bug report: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939537/+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 1939537] Re: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases
I am attaching a fix for Bionic. Note that this pulls in another unapproved change from @xnox to ease merging in time for the SRU cycle. This was checked with Stéphane Graber, who agreed to an exception of pushing a test-specific change given the SRU cycle is ending very soon, and most of the users would have switched anyway. ** Patch added: "lxc_3.0.3-0ubuntu1~18.04.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1939537/+attachment/5673160/+files/lxc_3.0.3-0ubuntu1~18.04.3.debdiff -- 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/1939537 Title: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: New Status in lxc source package in Bionic: New Bug description: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939537/+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 1939537] Re: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases
** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu Bionic) Assignee: (unassigned) => Andrei Gherzan (agherzan) -- 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/1939537 Title: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: New Status in lxc source package in Bionic: New Bug description: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939537/+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
