** Changed in: linux-firmware (Ubuntu)
Assignee: Seth Forshee (sforshee) => (unassigned)
--
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/1928393
Title:
linux-firmw
The commit reverts cleanly. We need to confirm that reverting the commit
does fix the issue. I put a test build here, please test.
https://people.canonical.com/~sforshee/lp1925211/
I doubt we can get a new kernel into the release. If it's extremely
urgent we can consider a day 0 SRU kernel for hi
The condition for css_sch_device_unregister(sch) also caught my eye,
calling it unconditionally is probably closer to right because it was
called in the !cdev case before, and in the attached patch it would no
longer be called in this case. However I think in the short term the
revert is the safest
** Description changed:
+ SRU Justification
+
+ [Impact]
+
+ Hot removal of disks under kvm on s390 does not result in the kernel
+ removing the block device, which can lead to hung tasks and other
+ issues.
+
+ [Test Plan]
+
+ See steps to reproduce the bug in the original description below.
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-canonical-kernel-team-bootstrap/hirsute/amd64/l/lxc/20201208_183047_03358@/log.gz
arm64:
https://objectstorage.prodstack4-5.canonic
lxc-test-api-reboot fails. The container fails to start, I see lots of
errors in the logs related to mounting things.
--
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/1907307
Titl
Public bug reported:
Ubuntu carries a patch for gdb, ptrace-error-verbosity.patch, to print
some extra information about why attaching to a process might have
failed. This inserts a fprintf_unfiltered() call between the ptrace()
and the corresponding perror(). Recently something has changed which
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
--
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/1818204
Title:
Qualcomm Atheros QCA9377 wir
Public bug reported:
In running adt testing on 5.2-based kernels for eoan, I'm seeing
failures from the apparmor mult_mount regression test. Running the test
case manually with -x yields:
+ dd if=/dev/zero of=/tmp/sdtest.2210-22387-i6UxxQ/image.ext3 bs=4096 count=20
+ mkfs.ext2 -F -m 0 -N 10 /t
** Changed in: linux (Ubuntu)
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/1845317
Title:
Add new pci-id's for CML-S, ICL
Statu
Public bug reported:
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/
On Fri, Oct 18, 2019 at 03:03:43PM -, Christian Brauner wrote:
> Is this a flake or consistently reproducible?
It's reproducible.
--
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/b
Seems /dev/network_latency was removed upstream.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c3082a674f46fe49383b157882c41dfabaa37113
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ub
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/n/network-manager/20190710_160945_9116e@/log.gz
i386:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a8
Seems to possibly be something going slightly slower with this kernel.
With 5.2 a fw IPv6 address assignment tests (DHCP and RA) fail sometimes
and pass other times, and usually at least one of them fails. The same
failures would happen in the past, but less frequency. I suspect that
something is
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/s/systemd/20190724_134818_5c46d@/log.gz
arm64:
https://objectstorage.prodstack4-5.canonical
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/l/lxc/20190724_132232_e90e9@/log.gz
arm64:
https://objectstorage.prodstack4-5.canonical.com
We've also seen regressions with lxc which atm appear to be related to a
regression in mounting sysfs in containers which use user namespaces
(bug 1837888 for reference, though there's no activity on the bug as of
yet, just some irc discussion about the regression).
--
You received this bug notif
Ok, sorry, I see the description of your problem now. It was mixed in
with the automatically collected information, so I missed it initially.
However I still don't really see anything in the logs to explain the
symptoms you're reporting. Could you check the /var/log/kern.log* files
and see if you
He means that you are running a kernel from eoan-proposed, despite your
saying that you do not have updates from the -proposed pocket enabled.
This report contains no useful information about the crash you are
seeing. I see no indication of a kernel panic or anything like that in
the logs, despite
This was an upstream regression with mounting within user namespaces. It
has been fixed, closing the systemd bug as invalid.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
To clarify, this was an upstream *kernel* regression.
--
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/1837894
Title:
systemd 240-6ubuntu9 ADT test failure with linux 5.3.0-
Christian: Discussed this bug with stgraber last week. Sounds like
/dev/network_latency is just an arbitrary device picked for a test case,
and since it's been removed upstream a different device should be used.
He said you could get this fixed.
** Changed in: lxc (Ubuntu)
Importance: Undecided
Do you have an ETA on when you'll do an lxc upload with the fix?
--
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
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-bootstrap/focal/amd64/l/lxc/20191218_145013_76e0c@/log.gz
arm64:
https://objectstorage.prodstack4-5.canonical.c
I'm afraid that the firmware files just look to be pulled out of Windows
drivers downloaded from arbitrary download sites. I'd be hesitant to
stick those into our linux-firmware package in any case, and without a
license which allows us to redistribute the files we simply cannot
distribute them in
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to s
This is not a problem with linux-firmware itself, it does is trigger a
rebuild of the initrd for all installed kernels but it's initramfs-tools
which does this. It will try to generate an initrd for all kernels with
a file in /var/lib/initramfs-tools, so it sounds like you have a file
there for tha
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz
i386:
https://objectstorage.prodstack4-5.canoni
Public bug reported:
Testing failed on:
s390x:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/s390x/n/network-manager/20180613_112923_bf26d@/log.gz
** Affects: network-manager (Ubuntu)
I
Public bug reported:
== SRU Justification ==
Impact: The 4.15 hwe kernel includes some package shuffling, so the
VersionedKernelPackages list in /etc/apt/apt.conf.d/01autoremove needs
to be updated to include linux-modules* packages.
Fix: Backport the conf file changes from bionic.
Test Case: C
** Patch added: "apt_1.2.26ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1778551/+attachment/5156479/+files/apt_1.2.26ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
htt
Hmm, now that I actually look at how the file is used, I guess we could
verify the list generated by /etc/kernel/postinst.d/apt-auto-removal,
couldn't we?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://
Other than simply checking the patterns in the file, I can't think of an
easier way to test. If you know of one please let me know. I do
currently have a vm set up to let me test it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
Tests were previously getting skipped for s390, due to "Restrictions:
... isolation-machine" in the test control file. Possibly some sort of
infrastructure problem detecting that the tests are running in a
container.
--
You received this bug notification because you are a member of Ubuntu
Touch s
Seems that s390x ADT does now run in VMs, which explains the change.
Since we don't have wireless support in our s390x kernels, these
failures are expected. Seems the tests will need to be changed to skip
these tests or make them expected failures.
--
You received this bug notification because y
Public bug reported:
Testing failed on:
i386:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/s/systemd/20171118_221900_c23d7@/log.gz
s390x:
https://objectstorage.prodstack4-5.canonic
Oops, didn't mean to file this yet as tests haven't completed. However
there are failures already.
On s390x, the test history leads me to believe that the tests started
failing when we switch to running tests in VMs.
Traceback (most recent call last):
File "/tmp/autopkgtest.EztoIW/build.0Oh/src
** Description changed:
Testing failed on:
- i386:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/s/systemd/20171118_221900_c23d7@/log.gz
- s390x:
https://objectstorage.prodstack4-
amd64 also passed on retry. s390x failure is present with 4.13 kernel
too, so not a regression in 4.14.
--
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/1733328
Title:
syste
** 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/1733328
Title:
systemd 235-2ubuntu3 ADT test failure with linu
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1717224
Title:
virsh start of virtual guest domain f
** Changed in: linux (Ubuntu Cosmic)
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/1762385
Title:
dell_wmi: Unknown key codes
S
** Changed in: linux (Ubuntu)
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
** Changed in: linux (Ubuntu)
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
** Changed in: linux (Ubuntu)
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 pre
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-unstable/cosmic/amd64/l/lxc/20180816_134239_340a6@/log.gz
arm64:
https://objectstorage.prodstack4-5.canonical.
Public bug reported:
Testing failed on:
i386:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-unstable/cosmic/i386/s/systemd/20180816_145803_9e627@/log.gz
s390x:
https://objectstorage.prodstack4-5.canonica
Added xenial nomination for initramfs-tools to add vmd.ko to initrd for
16.04.4.
** Also affects: initramfs-tools (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/s/systemd/20171025_152041_0db62@/log.gz
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** T
When I run the systemd tests locally using autopkgtest I cannot
reproduce this failure.
** Tags removed: kernel-adt-failure
** Tags added: kernel-adt-failure-hwe-edge-4.13
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to syste
boot-smoke test fails:
checking that there are no running jobs
FAIL: expected: '' actual: '550 lightdm.service start running'
--
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/
>From journal.txt in the adt artifacts:
Oct 25 13:55:35 autopkgtest systemd[1]: lightdm.service: Main process exited,
code=exited, status=1/FAILURE
Oct 25 13:55:35 autopkgtest systemd[1]: lightdm.service: Unit entered failed
state.
Oct 25 13:55:35 autopkgtest systemd[1]: lightdm.service: Failed
autopkgtest [13:37:31]: test wpa-dhclient: [---
modprobe: FATAL: Module cfg80211 not found in directory
/lib/modules/4.14.0-6-generic
ERROR
==
ERROR: setUpClass (__main__.T)
---
Public bug reported:
Testing failed on:
s390x:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/n/network-manager/20171107_135937_02323@/log.gz
** Affects: network-manager (Ubuntu)
I
This and other errors are related to lacking the cfg80211 module, which
we do not build for s390. However we did not build it in artful either,
and we currently have the same version of network-manager in artful and
bionic, so it's odd that the tests are failing in bionic and not in
artful.
--
Yo
I'm not sure why this was reported against alsa-drivers, you didn't
report any alsa packages in those that were upgraded when the problem
started. To get the bug noticed it's helpful to report the bug against
the appropriate package. If you believe the issue is related to a linux-
firmware update t
Losing the state when using the network indicator sounds like a network-
manager bug, so I'm going to change this to affecting that package. The
issue when using a key could be caused by network-manager, the kernel,
or your system firmware depending on how it's implemented for your
machine.
** Pac
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification because you are a member
I have a fix, but I will want to run it by upstream before we apply it
to be sure we aren't opening up any security issues. In the meantime
I've put up a test build, please give it a try and verify that the uuid-
runtime upgrade can be successfully installed.
http://people.canonical.com/~sforshee/
In addition to the requested logs could someone provide steps to
reproduce, preferably in a VM without MAAS?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to eglibc in Ubuntu.
https://bugs.launchpad.net/bugs/1464442
Title:
i
I've also reproduced it in a VM using Stefan's method. Both Stefan and I
have verified that stubbing out or removing /etc/init/mounted-tmp.conf
eliminates the problem, so it seems that this job is getting triggered
somehow.
--
You received this bug notification because you are a member of Ubuntu
Also I forgot to mention that Chris Arges pointed out that there's a
eglibc postinst script which does a re-exec of upstart, which is an
important piece of the puzzle.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to eglibc in
http://paste.ubuntu.com/11768305/
That link shows upstart-monitor output during the libc6 upgrade. I see
the mountall job starting, then later I see a mounted event for /tmp
which triggers the mounted-tmp job, which is what ends up clearing out
/tmp. In fact, generally it looks to me like many of
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
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/1703339
Title:
Unable to insta
Public bug reported:
The longpath regression tests tries to write to
/sys/module/apparmor/parameters/path_max, but this is read-only in
artful/4.11:
commit cdc8e09e16bb7eb7d23fcbdbe416aa91770fb4d6
Author: John Johansen
Date: Thu Apr 6 05:14:20 2017 -0700
apparmor: Make path_max parameter
What if the test was changed to check writability of path_max? Just
changing the the check for the sysfs path to -w won't work for root, but
maybe something like this (perhaps there's a simpler way to do the check
though):
if [[ -f /sys/module/apparmor/parameters/path_max &&
$(stat -c "%a" /
Something more like this then.
if [ ! -f /sys/module/apparmor/parameters/path_max ] ; then
echo "WARNING: This version of AppArmor does not support changing
buffer size."
else
mode=$(stat -c "%a" /sys/module/apparmor/parameters/path_max)
if (( 8#$mode & 0222 )); then
Public bug reported:
ADT boot-smoke test fails with 4.10 hwe-edge kernel in xenial.
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial/xenial/amd64/s/systemd/20170329_130746_29365@/log.gz
checking that there are no running jobs
FAIL: exp
Here's an example with the test passing for the same kernel/systemd
versions as fail later (4.10.0-15/232-19):
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-zesty/zesty/amd64/s/systemd/20170328_002748_44e26@/log.gz
--
You received this bug
Public bug reported:
In recent ADT runs TEST-03-JOBS has started failing with various systemd
versions. Here's one with 232-19:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-zesty/zesty/amd64/s/systemd/20170403_174708_e037b@/log.gz
and ano
Note that the "error: org.freedesktop.systemd1.NoSuchUnit: Unit
c.service not found." is reported in bug #1672499.
--
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/1679764
Tit
autopkgtest [17:28:29]: test boot-smoke: [---
reboot #0
bash: line 1: 32362 Killed
/tmp/autopkgtest.eXsKq9/build.l7Q/systemd-232/debian/tests/boot-smoke 2> >(tee
-a /tmp/autopkgtest.eXsKq9/boot-smoke-stderr >&2) > >(tee -a
/tmp/autopkgtest.eXsKq9/boot-smoke-s
Public bug reported:
Testing failed on:
armhf:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/armhf/s/systemd/20170329_172954_1ba5b@/log.gz
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tag
Confirmed that the test in the 232-21ubuntu3 source package no longer
hangs.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bug
Zesty already has the latest 7260 firmware (revision 459231), and
according to the attached CurrentDmesg.txt that's what being using:
[8.000329] iwlwifi :01:00.0: loaded firmware version 17.459231.0
op_mode iwlmvm
--
You received this bug notification because you are a member of Ubuntu
T
Public bug reported:
We're seeing intermittent kernel ADT test failues against network-
manager due to the ColdplugWifi test timing out. This is happening
across multiple releases. Here's an example from xenial:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153
Public bug reported:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-zesty/zesty/armhf/s/systemd/20170310_221057_b5cf9@/log.gz
root-unittests fails:
-> Unit a.service:
Description: a.service
Instance:
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/s/systemd/20170313_204550_ecb32@/log.gz
i386:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3
The cause seems to be that TEST-12-ISSUE-3171 is hanging. I've
reproduced the problem with the 4.10.0-11 and 4.10.0-13 kernels and with
systemd 232-18ubuntu1 and 232-19. I'm attaching the journal from one of
the test runs, taken from within the nspawn container while the test was
hung (using linux
Public bug reported:
debian/tests/exercise fails if http_proxy is not set, e.g.:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-zesty/zesty/amd64/l/lxc/20170320_194539_28897@/log.gz
Since the script uses 'set -e' the expression 'if [ -n "${
It does seem to be something in zesty. Not in the kernel though, I tried
xenial and yakkety kernels with zesty userspace and still got the hang.
But when I use a zesty kernel with yakkety userspace I don't see it.
--
You received this bug notification because you are a member of Ubuntu
Touch seed
Public bug reported:
Testing failed on:
s390x:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/s390x/s/systemd/20170728_111056_ccb5f@/log.gz
** Affects: systemd (Ubuntu)
Importance: Undeci
autopkgtest [11:09:53]: test boot-smoke: [---
...
checking that there are no running jobs
running jobs after remaining timeout -1:
61 apt-daily-upgrade.timerstart waiting
209 systemd-hostnamed.service start running
64 NetworkManager-wait-online.service sta
Public bug reported:
Testing failed on:
armhf:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170814_062054_7f9b9@/log.gz
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** T
networkd-test.py FAIL non-zero exit status 1
root-unittests FAIL non-zero exit status 1
networkd-test:
==
FAIL: test_catchall_config (__main__.UnmanagedClientTest)
Verify link states with a catch-all config, hot-plug.
There are quite a few messages like these that lead me to believe where
running out of inotify watches.
Failed to acquire watch file descriptor: Too many open files
path-exists.path: Failed to enter waiting state: Too many open files
--
You received this bug notification because you are a member
armhf failure:
==
FAIL: test_search_domains_too_long (__main__.NetworkdClientTest)
--
Traceback (most recent call last):
File "/tmp/autopkgtest.WNuNXs/build.mwP
Public bug reported:
Testing failed on:
armhf:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170823_191459_e2f1d@/log.gz
s390x:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a8492
s390x failure:
autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt
pinning. Retrying with using all packages from proposed
Reading package lists...
Building dependency tree...
Reading state information...
Correcting dependencies...Starting pkgProblemResolver with broken count
armhf passed after re-running, so I guess we can ignore it. Since the
s390x failure is fixed in -proposed I'll close the bug as invalid, I can
hint away the kernel test failure since it's clearly not a kernel issue.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received th
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/l/lxc/20170825_140357_85137@/log.gz
i386:
https://objectstorage.prodstack4-5.canonical.c
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/l/lxc/20170829_024349_c4b5f@/log.gz
i386:
https://objectstorage.prodstack4-5.canonical.c
Public bug reported:
Testing failed on:
ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/systemd/20170906_131209_2a96a@/log.gz
** Affects: systemd (Ubuntu)
Importance: Un
With the latest upload tests still fail, but it seems to get slightly
farther. Is this a different issue?
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-artful-canonical-kernel-team-
unstable/artful/amd64/l/lxc/20170906_003748_d668f@/log.gz
I see adt failures with 4.12 as well, looks like a regression in
ppc64-diag. Changing affected package.
** Package changed: systemd (Ubuntu) => ppc64-diag (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ub
ep 06 12:23:41 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]:
Starting ppc64-diag rtas_errd (platform error handling) Service...
Sep 06 12:23:41 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]:
Started ppc64-diag rtas_errd (platform error handling) Service.
Sep 06 12:23:
This patch fixes the tests for me. Turns out that we can't simply skip
writing to path_max as that seems to break the test case completely, so
I changed it to print an XFAIL message and abort the test.
** Patch added: "fix-longpath-test.patch"
https://bugs.launchpad.net/ubuntu/+source/apparmor
Public bug reported:
Testing failed on:
ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/systemd/20170627_083238_11cda@/log.gz
** Affects: systemd (Ubuntu)
Importance: Un
E: /usr/share/initramfs-tools/hooks/casper-memdisk failed with return 1.
This seems to be related to an initramfs hook for casper, so marking
this bug as also affecting casper.
** Also affects: casper (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification bec
1 - 100 of 172 matches
Mail list logo
