Setting to invalid as this was not a test failure, but the result of the
test being interrupted due to a timeout.
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to
Actually, it looks like all focal images and seems non-arch specific.
Focal containers back to serial 20200609 exhibit this behaviour of having an
fstab.
http://cloud-images-archive.ubuntu.com/releases/focal/release-20200609/
** Changed in: cloud-images
Status: New => Confirmed
** Summa
Here's a reproducer with ancient amd64 images:
$ lxc launch ubuntu:ffae848ee5a0 tstf
Creating tstf
$ lxc exec tstf bash
root@tstf:~# cat /etc/fstab
LABEL=cloudimg-rootfs /ext4 defaults0 0
root@tstf:~# cat /etc/cloud/build.info
build_name: server
serial: 20200529.1
root@tstf:~
Short reproducer:
$ lxc init ubuntu:focal/armhf focal-test
Creating focal-test
$ lxc start focal-test
$ lxc exec focal-test /bin/bash
root@focal-test:~# systemctl is-system-running
degraded
With some further diagnostics:
root@focal-test:~# systemctl list-units | grep failed
● systemd-remount-fs.s
Tim Andersson has proposed merging
~andersson123/autopkgtest-cloud:copy-security-group-more-robust into
autopkgtest-cloud:master.
Requested reviews:
Canonical's Ubuntu QA (canonical-ubuntu-qa)
For more details, see:
https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-c
This issue resurfaced recently, e.g. with trusty:linux 3.13.0-201. The
root cause might be different, I suspect it might be related to trusty
missing upstream fix
2e356101e72a KEYS: reaching the keys quotas correctly
so this test is failing similarly to add_key05 (LP: #1879906) which was
fixed fo
Tim Andersson has proposed merging
~andersson123/autopkgtest-cloud:worker-nova-client-robustness into
autopkgtest-cloud:master.
Requested reviews:
Canonical's Ubuntu QA (canonical-ubuntu-qa)
For more details, see:
https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-clo
** Summary changed:
- ubuntu_ltp cve-2018-1000204 ioctl_sg01.c:118: TFAIL: Kernel memory leaked for
oracular/noble on kopter (arm64)
+ ubuntu_ltp_cve cve-2018-1000204 ioctl_sg01.c:118: TFAIL: Kernel memory leaked
for oracular/noble on kopter (arm64)
--
You received this bug notification becaus
pids_9_50 fails in a similar fashion for bionic:linux in s2024.10.28 on
kernel02.s390x.
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2085826
Title:
ubuntu_ltp_controller
Newest code works just fine for that use-case:
https://autopkgtest.ubuntu.com/results/autopkgtest-oracular-cpete-
bonnie++/oracular/amd64/b/bonnie++/20241202_143911_dbf48@/log.gz
Closing the bug.
** Changed in: auto-package-testing
Status: In Progress => Fix Released
--
You received this
Test shows this node "recht "will require 3h44m for
ubuntu_ltp_controllers test execution. The cpuset_load_balance timeout
with 4500 sec.
I think this is the main reason why the test timeout in the middle.
And for ubuntu_ltp, it needs 4h7m to run. All tests passed with the extended
timeout.
This
** Also affects: cloud-images
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launchpad.net/bugs/2089380
Title:
focal armhf instances boot in degraded
@Skia: I believe you fixed this already by making autopkgtest-cloud use
the --add-apt-source=ppa:... syntax.
** Changed in: auto-package-testing
Assignee: (unassigned) => Skia (hyask)
** Changed in: auto-package-testing
Status: New => In Progress
--
You received this bug notificatio
For bionic:linux 4.15.0-232.244 in s2024.10.28 this test fails similarly
but does not hang the device immediately. It will continue to run
cpuhotplug05 which passes, while the next test cpuhotplug06 fails in the
same manner as cpuhotplug04 and subsequently hangs the system.
07:33:50 DEBUG| Persist
Ural Tunaboyu has proposed merging ~uralt/autopkgtest-cloud:ppa-endpoint into
autopkgtest-cloud:master.
Requested reviews:
Canonical's Ubuntu QA (canonical-ubuntu-qa)
For more details, see:
https://code.launchpad.net/~uralt/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/477579
Add a new /ppa
ubuntu/production updated to be626eda6f4b21.
** Changed in: auto-package-testing
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launchpad.net/bugs/2089
Setting to invalid as this was not a test failure, but the result of the
test being interrupted due to a timeout.
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to
Public bug reported:
I saw the following issue on oracular (6.11.0-12.13) and noble
(6.8.0-50.51) kernels for 2024.10.28 cycle on metal:kopter (arm64). I
suspect this is not a new regression. Rather we started getting this
error after introducing new instances.
INFO: Test start time: Fri Nov 22
I have come across the same "no space left on device" issue for the following
tests (on oracular 6.11.0-12.13 - 2024.10.28):
- ubuntu_qrt_apparmor
- ApparmorTestsuites.test_parser_testsuite
- (oracle:VM.Standard.A1.Flex-4c.8m)
- (openstack:ppc64el-vm)
- (openstack:builder-arm6
19 matches
Mail list logo