Thanks Chris for having a look.
> On the other hand, from the bug it looks like if you *don't* mix valid and
> invalid labels
> then everything actually works? So this would potentially be breaking
> currently working setups?
Yes while having that echoing in my head for a while I think you are
** Changed in: dnsmasq (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
** Tags removed: needs-merge
** Tags added: needs-sync
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
ht
Hi Christian,
I saw both, the close and your question.
I'd assume that Steve is updating those in a semi-automated fashion, there is
no way he could read all those bugs.
Per bug status this one is marked fixed and only had a bug task open to
backport to Precise.
In fact the upstream commit that
** No longer affects: libvirt (Ubuntu 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/1875708
Title:
Truncated messages in journald since systemd v244
Status in
Reviewed and tested - uploading to Bionic-unapproved for a check by the
SRU Team.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1662620
Title:
"ip addr add" permits
And a PPA with a test build
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4676/+packages
** Tags added: server-todo
** Changed in: iproute2 (Ubuntu Bionic)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
** Description changed:
+ [Impact]
+
+ * The filter on la
SRU template added
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1662620
Title:
"ip addr add" permits illegal labels
Status in iproute2 package in Ubuntu:
Fix
Hi,
I come by trying to clear out a few old bugs that might still need to be
resolved (or can be closed by now).
Even though this one seems to be forgotten by everyone so far it has
been fixed.
Bionic (affected)
root@b:~# ip addr add 1.1.1.1 label test1 dev eth0
"dev" (eth0) must match "label"
@Miriam - please consider applying [1] to impish and later on the same for the
SRUs.
Let me know if the test steps that I created based on all the discussions would
not work for you.
This can then, down the road become a sync again once there is 0.8.16
released.
[1]:
> Christian, thank you for stepping in. It seems you finally got the ball
> rolling
> here where I was unsuccessful in a good half dozen attempts in #ubuntu-devel
> and other venues. That's the good news I suppose.
Np, glad to help - although this time as you said it was more "stepping
in" as I
** Description changed:
+ Steps to reproduce (for later SRU work)
+
+ #0
+ # On the test Host install apt-cacher-ng
+ # you need to do so before creating the guest to propagate
+ # and configure correctly when spawned
+ $ sudo apt install apt-cacher-ng
+
+ #1
+ # create a VM guest or container
I've dupped another case onto this, it stays an issue that from the libvirt
side has been handled by
https://gitlab.com/libvirt/libvirt/-/commit/8c70d04bab7278c96390a913fa949a17cd3124f9
which is in >=Bionic.
AFAIU remaining issues as outlined in comment #2 are still considered
more an
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs integration for
Hi Rolf,
let me try to calm things down a bit via clarifications on the
technical and ubuntu-process side of this.
> I'm not sure I understand what you did and what your results were. It
> appears that you got the issue of an "uncaptured python exception" at
> least once "when you removed
** Description changed:
I get the following error when running the discovery script on the
command line.
$ /usr/share/squid-deb-proxy-client/apt-avahi-discover
error: uncaptured python exception, closing channel
('10.1.2.3', 3142): 2147483647 (:[Errno 111] Connection
refused
Martin, I almost expected that would be the call but wanted to leave it to you
to decide.
Thank you as always!
o/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to umockdev in Ubuntu.
https://bugs.launchpad.net/bugs/1945321
Held back in proposed migration:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/a/autopkgtest/20210929_062309_c71f0@/log.gz
That test fail can't be reproduced in local autopkgtest (LXD init is
different in the autopkgtest infra compared to a "normal" cloudimage)
nor does
Since Debian is also affected I filed it there as well:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995248
** Bug watch added: Debian Bug tracker #995248
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995248
** Also affects: umockdev (Debian) via
** Changed in: bolt (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to umockdev in Ubuntu.
https://bugs.launchpad.net/bugs/1945321
Title:
umockdev 0.16.3-1 breaks autopkgtest of
Looking at the changelog this looks suspicious:
- Immediately create "bus" and "class" directories in /sys to fix udev
enumerator (thanks David Lechner)
That change is at
https://github.com/martinpitt/umockdev/commit/5e829601434610ef510bda12571291509a3a51d2
And that explains it,
Public bug reported:
The test of bolt fails with the new version due to a crash:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/b/bolt/20210917_063952_c9336@/log.gz
...
Trace/breakpoint trap (core dumped)
The bolt test really uses umockdev, d/t/control has
I have again updated the upstream case, but if they are not willing/convinced
this won't happen as Ubuntu delta or we will have too many small scratches by
being slightly different on this.
So anyone affected/requesting this please chime in on the upstream bug.
Dropping server-next as it can't
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1941799
Title:
Please merge openssh 1:8.4p1-6 from Debian unstable
Status in openssh package
** Changed in: docker.io (Ubuntu)
Status: New => Invalid
** Tags removed: server-next
--
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/1916485
Title:
test -x fails
The tests are skipped in autopkgtest as they used to (for SRU non
changing behavior we kept it that way) but on build time where they
before sometimes broke things via flakiness no issues are seen on this
build.
Setting verified for this bug.
** Tags removed: verification-needed
Test built the test-modified version and uploaded to Hirsute-unapproved
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1939861
Title:
dpdk: ppc64el autopkgtest
** Description changed:
+ [Impact]
+
+ * Some tests (just a small portion of a vast list of tests) is not really
+breaking due to real issues but just happen to be notorious timeouts
+or flaky in the Ubuntu build environment.
+
+ * We have fixed that in Debian and Impish already, but
On Mon, Sep 6, 2021 at 4:05 PM Dan Streetman <1785...@bugs.launchpad.net> wrote:
>
> > [commenting so the bug doesn't get expired as we still need to look at
> the Bionic fix for dnsmasq]
>
> AFAIK, launchpad bugs only auto-expire if set to 'incomplete'. bugs set
> to anything else, like this one
Yeah that would be fine, we have assigned two FTFBSes but not yet this one.
Take it and thanks in advance.
I mean your debdiff could already be all that is needed - but is it test-built,
tested, discussed and so on.
If you need any help/review please ping us here.
** Changed in: openssh
Thank you, options are discussed.
I'll set the bug to incomplete to reflect this isn't blocked on security right
now.
** Changed in: busybox (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
>From the log:
Bind to port 22 on 0.0.0.0 failed: Address already in use.
Something on your system already blocks the default SSH port which the
service will try to consume on install/update. You'd want to find what
owns this port and remove/reconfigure that - afterwards the openssh-
server
This update includes one of the two changes we have as delta.
Another Fix (group collisions) and the fix for this issue here.
I think despite FF, this could be re-merged to resolve this and the other
mentioned bugs.
I'll tag it to be more likely to be considered.
But to avoid collisions
Yeah, only hanging on glibc indeed.
Since the reported test fail is fixed let us mark it "fix released", that way
it shows only the glibc transition and not the (now fixed) update excuse bug in
update-excuses.
** Changed in: dpdk (Ubuntu)
Status: Triaged => Fix Released
--
You received
Now passing
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/d/dpdk/20210816_082513_d8152@/log.gz
It should soon have all tests complete (so far no failures) and migrate.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Hi,
since the obvious solution (ExecStop) was found to be bad as it introduces a
regression and it is no more even clear on which level it has to be solved
(systemd, openssh in Debian, openssh in Ubuntu) I think this is no more
as-actionable as before.
Sure if someone has the time (or just
Still the systemd tests are very flaky.
I went through some re-runs and these last 7 tests all did test the very same
packages.
impish
amd64
boot-and-services (F 14% f 0% S 0% B 0% => P 85%/) ...F...
systemd-fsckd (F 0% f 0% S 100% B 0% => P 0%/)
While some other flaky tests still hold it back the issue is fixed.
Here the PPC test of the new upload:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20210714_130923_091d6@/log.gz
--
You received this bug notification because you are a member of Ubuntu
Touch
Ok, now that we know the root cause we can mark systemd as invalid and the ppc
project as fixed.
The qemu task will be fixed once the upload migrates - but currently the test
queue is rather full.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
** Changed in: ubuntu-power-systems
Ok, that fix works fine in a test.
I'm uploading this for a full test and hope that there are no further issues
with it that were hidden behind it so far.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
After some setup and preparation I was bisecting through v5.2.0..v6.0.0
to see which change exactly added this new behavior.
Summary:
- build reduced qemu
- build, configure and log-check errors will be skips
- run the extracted systemd test
- redirect serial to file
- check log if the
And that matches:
Offending commit:
bcb0b7b1a1c05707304f80ca6f523d557816f85c is the first new commit
commit bcb0b7b1a1c05707304f80ca6f523d557816f85c
Author: Giuseppe Musacchio
Date: Mon Nov 9 10:17:11 2020 +0100
ppc/translate: Rewrite gen_lxvdsx to use gvec primitives
Make the
I've collected the instructions that are around the failures and it is
suspicious for
lbzx / lvx / ld
All failures are around those:
Impish
ubuntu@i-systemdtest:/var/crash$ for i in */CoreDump; do p=$(dirname $i | tr -d
'.0123456789' | tr '_' '/' ); gdb $p $i -q -ex "x/-10i \$pc" -ex "x/3i
Hmm, I can blindly read through the qemu commit log and try rebuilds or even a
bisect at some point. But maybe this is already known. Since I'm soon on EOD I
wonder if we could mirror this to IBM (now that we know a bit more) if this is
a known issue to point us at an existing discussion or
We've had similar cases int he past where new releases glibc or compiler had
new instructions breaking the TCG mode.
So I spawned a focal and a bionic image - and then remodeled them to run in
emulation mode.
And indeed Bionic works without any crashes, so it must be something in the
guest
quotearg seems to be from gettext
https://sources.debian.org/src/gettext/0.21-4/gettext-tools/gnulib-lib/quotearg.c/?hl=1#L1
And is at least related in a few of the crashes (but not exclusively).
I wonder if the new TCG implements an instruction differently that now breaks.
--
You received
Backtraces
Two times (on rm, only slight variations)
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x0798b9f361d0 in quotearg_buffer_restyled
(buffer=buffer@entry=0x798b9f60130 "'",
buffersize=buffersize@entry=256,
arg=arg@entry=0x800369e19807 ,
I installed a ppc64 impish cloud image (all fine) but then ran it in TCG
mode (to check if I can trigger the same).
That starts it like:
/usr/bin/qemu-system-ppc64le -name guest=i-systemdtest,debug-threads=on -S
-object
>From here I was switching to qemu 6.0 on the bare metal machine.
6.0-KVM - works
6.0-TCG - works
But running the testsuite itself fails (due to using only 512M ram).
I found that switching from testsuite-08 to testsuite-09 allowed me to get into
bad-mode in TCG (with enough memory, but into the
Since the bare metal case reports a memory issue on the crashes, let us
give it a bit more memory - with 2G it works finally.
Instead of the other tests in launchpad/canonistack this uses KVM mode
via "-machine accel=kvm -enable-kvm -cpu host". Switching that instead
to "-machine accel=tcg" it
I tried the same on a bare metal machine (now one is available for a
short time).
Got the new systemd source and test, ran it with qemu 5.2 and it is failing.
But not randomly, the same subset of tests fails on bare metal with 5.2.
But now they all fail on an OOM.
kvm: OS terminated: OS
The service has a StartPre that is like
ExecStartPre=rm -f /failed /testok
And that works to reproduce:
bash-5.1# rm -f /failed /testok
Segmentation fault (core dumped)
In fact this RM is very very sad:
-bash-5.1# rm /doesnotexist
Segmentation fault (core dumped)
-bash-5.1# touch /doesexist
As root:
$ mkdir /tmp/debugtest
$ export ARTIFACT_DIRECTORY=/tmp/debugtest
$ export TEST_SHOW_JOURNAL=warning
$ export TEST_REQUIRE_INSTALL_TESTS=0
$ export TEST_PREFER_NSPAWN=1
$ export NO_BUILD=1
$ export SELECTED_TESTS="TEST-08-*"
./test/run-integration-tests.sh
Reproduces the issue, it will
Isolated case
$ sudo env SELECTED_TESTS="TEST-08-*" debian/tests/upstream
It runs a VM Guest to do init stuff and that seems to break:
There are suspicious logs like systemd crashing, but those also exist
(to some extent) in the good case. I compared that:
$ grep -e "of user 0 dumped core" -e
While canonistack was breaking hard on me last week I managed to get an
instance running today.
Trying to reproduce the issue in there ...
Atfer a long while of upgrades, dependencies,
I was running with impish (as-is) vs impish+qemu6.0.
It was very reproucible working with 5.2 and always
> product engineering has access to PPC systems in maas?!? sigh...that sure
> would be nice
> for sustaining engineering to have access to also :(
That might sound more appealing than it is, the HW is often broken the
availability is worse than gold-nuggets and I think I never got a system
My Repro-tests indeed seem to indicate that really qemu 6.0 is the trigger for
this,
but as I said HW is rather unavailable at the moment. I was told that the MAAS
is serviced but should be back soon - so I'll have a look later when this one
is available again.
--
You received this bug
Public bug reported:
I'm not sure yet if this is flaky or a real issue, but I'm filing it to
avoid multiple people analyzing the same.
The Qemu 6.0 upload
https://launchpad.net/ubuntu/+source/qemu/1:6.0+dfsg-1~ubuntu2 triggers a test
failure like
The DNSmasq change is in impish as well.
Since we (intentionally) referenced but not closed the bug by the upload I'll
have to tag that manually.
** Changed in: dnsmasq (Ubuntu Impish)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of
dnsmasq tested all fine with the new NM.
Only the odd systemd blocker holds us back now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1894619
Title:
[2.82 regression]
The new NM tests were fine (even against the old dnsmasq due to the or in the
regex).
NM hit a few non related systemd test issues - I re-triggered those.
Finally I did now start the new NM tests against the blocked dnsmasq.
Overall that should hopefully resolve both and let them migrate.
--
Ok, as planned I can reproduce this in local autopkgtest.
Multiple hits on:
AssertionError: Regex didn't match: 'inet6 2600::[0-9a-f:]+/64 scope global
(?:tentative )?(?:mngtmpaddr )?(?:noprefixroute )?dynamic' not found in '14:
eth42@veth42: mtu 1500 qdisc noqueue state UP
group default qlen
As expected this is now ready in proposed and blocked on the NM test, example:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/n/network-manager/20210701_151447_a29ef@/log.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
According to the discussion dnsmasq will revert to the upstream intended
behavior.
I added an open impish task to reflect that.
At the same time this makes network-mamager expose the test issue we initially
found it with.
An example can already be seen in
PPA:
I have not found any other test issues than the expected NM one.
So I'm uploading since - to some extend - we want to see if anything else
breaks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
Yes, having a centralized default available multi-size hugepage
mountpoints would still be nice to have.
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: systemd (Ubuntu)
Status: Won't Fix => Confirmed
--
You received this bug notification because you
** Changed in: busybox (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1933979
Title:
[MIR] busybox
Thanks for the feedback Stefan (and the Help Dan).
I'll mark the bug as invalid then as there is nothing to fix in a package for
it.
** Changed in: init-system-helpers (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch
Yeah I'm also not entirely sure.
But I'm assuming that the maintainers insight into all the interactions is
better than mine and therefore tend to follow.
About the "why the difference DHCPv6 vs SLAAC" I think that is fine
because the code now allows to behave different (reasonable). And the
We finally got an answer to our questions/pings (thanks Simon)
=> https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2021q2/015134.html
TL;DR: this might be wanted new behavior :/ ?!
@Laney - You initially started this when we have faced this bug
I wonder now if we should indeed drop our
The apparmor section of this is now properly covered in bug 1932537,
therefore I'm dropping the apparmor task from this one.
** No longer affects: apparmor (Ubuntu)
** No longer affects: apparmor (Ubuntu Focal)
--
You received this bug notification because you are a member of Ubuntu
Touch
Cups rightfully includes nameservices like:
#include
After our analysis in bug 1890858 I think it is fair to request an SRU
update apparmor in Focal (only needed there, see bug 1890858 for
details). As it would fix this element in Cups and
Thanks for the quick test, works for me as well.
The global verification-done tag might be needed as well for the tools to work,
adding that back.
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
FYI - Uploaded to Focal-unapproved
--
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/1890858
Title:
AppArmor profile causes QEMU/KVM - Not Connected
Status in apparmor
FYI MP
https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/404124
updated with the more restricted rule.
I also updated the PPA with the new rule.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Thanks Seth and Robert,
I'll follows Seth advise and for now propose (B) being the fix for libvirt.
But I'll add a task for apparmor (which carries abstraction/namespace) as that
still might be an avenue worthwhile to follow independent to this libvirt fix.
If more people speak up or we find more
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1761096
Title:
dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed
Status
** Changed in: openssh (Ubuntu)
Assignee: Colin Watson (cjwatson) => (unassigned)
** Changed in: openssh (Ubuntu Trusty)
Status: Triaged => Won't Fix
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Without the recent PPC fixes s390x was broken as well, so I'm not saying "the
ppc fixes broke s390x":
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-ppa-service-4577/impish/s390x/d/dogtag-pki/20210608_073451_f187d@/log.gz
Instead there seems to be a new crash affecting s390x
Reproducible, ppc64 is fixed and s390x broken by the latest 3.66 + fixes from
master.
Links:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-ppa-service-4577/impish/s390x/d/dogtag-pki/20210609_065306_2e698@/log.gz
** Branch linked: lp:~paelzer/gdebi/gdebi-fix-glib-2.68
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/1931394
Title:
With glib2 2.68 gdebi is an FTBFS (hangs)
Status in
This feels like a circle with nss/2:3.66-1ubuntu1~impishppa2 in
https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/4577/+packages now ppc64 works but s390x fails
with (on the surface) the same symptom as it started with in 3.63 :-/
I retriggered the tests to see if that is flaky or
Public bug reported:
Ubuntu https://launchpad.net/ubuntu/+source/gdebi/0.9.5.7+nmu5 is an FTBFS
https://launchpadlibrarian.net/542966965/buildlog_ubuntu-impish-amd64.gdebi_0.9.5.7+nmu5_BUILDING.txt.gz
The same https://launchpad.net/ubuntu/+source/gdebi/0.9.5.7+nmu4 worked
as it was builds
Also blocking isc-dhcp now, added a task
** Also affects: isc-dhcp (Ubuntu)
Importance: Undecided
Status: New
** Changed in: isc-dhcp (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
There is another fix in master that belongs to
https://bugzilla.mozilla.org/show_bug.cgi?id=1566124 - I've bumped my
PPA build to include both as it is worth a try if this fixes the current
ppc64 issues in v3.66.
Build of 3.66-1ubuntu1~impishppa2 started, later on I'll let the
autopkgtests run.
I was able to verify that a merge of 3.66 would on Ubuntu trigger the
very same bug that Debian has blocking the dogtag-pki test on powerpc64.
=> https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-
ppa-service-4577/impish/ppc64el/d/dogtag-
pki/20210608_031158_a9d4a@/log.gz
--
While we wait for 3.67 and maybe (Thanks Timo) for [1] I have ensured that we
have a 3.66 test build.
=> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4577/+packages
The check of it's delta also showed that we can drop a bit of it nowadays.
=>
FYI by tjaaltonen - there's another crasher in 3.66 on ppc64el..
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989410
So 3.66 won't be the "take this and it works" solution.
** Bug watch added: Debian Bug tracker #989410
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989410
--
You
Public bug reported:
The test of dogtag-pki is failing on the nss 3.63 that is in impish proposed.
Example:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/d/dogtag-pki/20210516_212719_e6522@/log.gz
Bad:
Installing CA into /var/lib/pki/pki-tomcat.
Installation failed:
As I said I tried to recreate this, but it worked.
It was fine under Focal/5.4.0-53-generic Host with the Impish-armhf container.
Upgrading the host to impish it Impish/5.11.0-16-generic still works fine.
It seems it only fails in autopkgtest infrastructure, not sure why yet
:-/
--
You received
Public bug reported:
Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf
before now slipping into a bad mode.
Now it seems all tests failed in boot-and-services by hanging until killed by
VirtSubproc.Timeout of autokgtest.
The last [1] test log has a bit more, it shows a
I was adding a few of the blocked packages as incomplete tasks to have
this bug update-excuse show up in excuses. Right now until we know
better I'd consider this a systemd issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Bug watch added: Debian Bug tracker #989378
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989378
** Also affects: dnsmasq (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989378
Importance: Unknown
Status: Unknown
--
You received this bug notification
Testing former status with 5.11.0-17-generic
Journal:
Add:
May 17 05:56:26 h kernel: crw_info : CRW reports slct=0, oflw=0, chn=1, rsc=3,
anc=0, erc=4, rsid=5
May 17 05:56:26 h kernel: crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3,
anc=0, erc=4, rsid=0
May 17 05:56:26 h kernel: virtio_blk
On Mon, May 3, 2021 at 10:20 AM Ludovic Rousseau
<1892...@bugs.launchpad.net> wrote:
>
> opensc-pkcs11.so is a PKCS#11 lib so the its API conforms to the
> standard defined in https://docs.oasis-
> open.org/pkcs11/pkcs11-base/v2.40/os/pkcs11-base-v2.40-os.html
Thanks Ludovic for adding the expert
Thank you Marco and Sebastien,
> * the launchpad buglist has been triaged a bit and fixed issues closed
Thanks!
>From your bug cleanup did you spot any kind of setup/HW that you want to
>restrict/exclude?
Was there any common pattern that makes up most of the formerly seen bad
reports?
> *
I was wondering if I could trigger the same issue on an lpar as it would
raise the severity IMHO. I have no claim on completeness of these tests
in regard to all that could happen. I tried what I considered low
hanging fruits in regard to this cross check.
Pre-condition each time
- a dasd
Hi Kaihenfeng,
Thanks for your patch suggestion! I'm semantically not sure it is the right
thing - to clarify your theory is that before it checked !resuming and before
had the check for !cdev maybe just to avoid a deference error. And now you
assume that instead of !cdev it should check if
Thanks Frank for adding the mirror request to this, because either way
we sooner or later want a discussion with the s390x developers on this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Thanks Seth.
I have verified 5.11.0-16-generic #17+lp1925211v202104201520 from the PPA and
can confirm that the issue is gone.
=> The revert works as a fix \o/
For the severity/urgency at least we now know that it is s390x only (not "good"
but reduces the amount of affected people).
I'll later
commit 8cc0dcfdc1c0e0be107d0288f9c0cf1f4201be62
Author: Vineeth Vijayan
Date: Fri Nov 20 09:36:38 2020 +0100
s390/cio: remove pm support from ccw bus driver
As part of removing broken pm-support from s390 arch, remove
the pm callbacks from ccw-bus driver.The power-management
1 - 100 of 1048 matches
Mail list logo
