New ceph hotfix releases for Nautilus (v14.2.21) and Octopus (v15.2.12)
have pushed this another release further.
** Description changed:
[Impact]
The `osd_fast_shutdown` option (available in Nautilus and enabled
by default) may cause the cluster log to receive too many entries
of
Another ceph bugfix release (v14.2.20) has pushed this one release
further, thus at least v14.2.21.
** Description changed:
[Impact]
The radosgw beast frontend in ceph nautilus might hit coroutine stack
corruption on startup and requests.
This is usually observed right at the
New ceph bugfix releases for Nautilus (v14.2.20) and Octopus (v15.2.11)
have pushed this another release further.
Also marking Hirsute as Fix Released (v16.2.0+.)
** Description changed:
[Impact]
The `osd_fast_shutdown` option (available in Nautilus and enabled
by default) may cause
Public bug reported:
[Impact]
The `osd_fast_shutdown` option (available in Nautilus and enabled
by default) may cause the cluster log to receive too many entries
of `osd.X reported immediately failed by osd.Y` on large clusters.
This happens as the monitor no longer receives the OSD message to
Adding target Ubuntu/Cloud Archive releases.
(note: Victoria and Wallaby have no ceph packages yet, thus marking as
Invalid.)
```
The new option should be available in the following Ceph releases:
- Pacific 16.2.0 [Hirsute+]
- Octopus 15.2.11 [Focal/Groovy; Ussuri+]
- Nautilus TBD (at least
** Description changed:
[Impact]
The radosgw beast frontend in ceph nautilus might hit coroutine stack
corruption on startup and requests.
This is usually observed right at the startup of the ceph-radosgw systemd
unit; sometimes 1 minute later.
But it might occur any time
Comments #1- #6: example stack traces and GDB debug snippets of the
issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921749
Title:
nautilus: ceph radosgw beast frontend coroutine stack
coredump #6
RIP address in stack is actually not an instruction address, but a stack
address (corrupted stack).
GDB searched hard for stack unwinding, and got a very long trace, that might
not be correct.
Oct 23 16:41:27 HOSTNAME radosgw[3572]: *** Caught signal (Segmentation
fault)
coredump #5
Oct 23 16:41:01 HOSTNAME radosgw[1616]: tcmalloc: large alloc
94195528343552 bytes == (nil) @ 0x7f97ec494887 0x7f97ec1cb1b2 0x7f97ec1ff948
0x7f97ec1d08be 0x7f97ec1db01e 0x7f97ec1dd433 0x7f97ec1e843d 0x7f97ec1e8680
0x7f97ec1afe3a 0x7f97ec1857ec 0x55ab96ae9dbc 0x55ab967d8a22
coredump #4
Shorter stack trace reported in ceph logs than in GDB.
Oct 23 16:41:28 HOSTNAME radosgw[4319]: *** Caught signal (Segmentation
fault) **
Oct 23 16:41:28 HOSTNAME radosgw[4319]: in thread 7fb79e999700
thread_name:msgr-worker-2
Oct 23 16:41:28 HOSTNAME
coredump #3
(gdb) bt
#0 raise (sig=sig@entry=11) at ../sysdeps/unix/sysv/linux/raise.c:51
#1 0x55bd9a04f6b0 in reraise_fatal (signum=11) at
./src/global/signal_handler.cc:81
#2 handle_fatal_signal (signum=11) at
./src/global/signal_handler.cc:326
coredump #1
(gdb) bt
#0 raise (sig=sig@entry=11) at ../sysdeps/unix/sysv/linux/raise.c:51
#1 0x555f023cf6b0 in reraise_fatal (signum=11) at
./src/global/signal_handler.cc:81
#2 handle_fatal_signal (signum=11) at
./src/global/signal_handler.cc:326
coredump #2
(gdb) bt
#0 raise (sig=sig@entry=11) at ../sysdeps/unix/sysv/linux/raise.c:51
#1 0x557c23db26b0 in reraise_fatal (signum=11) at
./src/global/signal_handler.cc:81
#2 handle_fatal_signal (signum=11) at
./src/global/signal_handler.cc:326
Public bug reported:
[Impact]
The radosgw beast frontend in ceph nautilus might hit coroutine stack
corruption on startup and requests.
This is usually observed right at the startup of the ceph-radosgw systemd unit;
sometimes 1 minute later.
But it might occur any time handling requests,
** Tags removed: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909950
Title:
named: TCP connections sometimes never close due to race in socket
teardown
To manage notifications
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: parted (Ubuntu)
Status: New =
Ack; will do. Thanks for the notice!
** Changed in: bind9 (Ubuntu Focal)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909950
Title:
named: TCP
For doc purposes, I've had an interesting time
debugging why the bind9 forwarding didn't work
to a host running dnsmasq/libvirt (DNS server).
After some tcpdump comparisons against a local
dig client that worked fine, it turns out that
dnssec-validation must be changed from 'auto'
to 'yes', and
Matthew,
Thanks for the great work on this bug. Sponsored to focal.
I've reviewed the debdiff and had only two minor changes:
1) the Description: field to conform with DEP3/deb822 [1,2]
on multiline field (first line and paragraph separators),
2) trimmed 'and-' of the patch name to keep its
and apport/amd64 played tricks on us, but it does pass now.
it passed on bionic-updates, which suggests a regression on bionic-proposed;
but another rereun with bionic-proposed now passed.. well. it's good now! :)
from [1]:
2.20.9-0ubuntu7.23 python-httplib2/0.9.2+dfsg-1ubuntu0.3
Heather and I discussed the autopkgtests failures today.
She's taking a look at fixing python-oslo.vmware, which
seems to be a missing Build-Depends: on python module(s)
nowadays, because the last time it passed was 2019-03.
It was reproducible with autopkgtests-virt-lxd locally.
For apport, it
** Tags added: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909950
Title:
named: TCP connections sometimes never close due to race in socket
teardown
To manage notifications
Some armhf autopkgtests finally ran, and unblocked mpd and samba.
Now re-running some systemd tests that have (again) been flaky, on amd64 and
ppc64el, to unblock qemu; the last piece missing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
That seemed to be correct; update_excuses is now updated,
and autopkgtests for mpd/samba/qemu are now running.
There were 3 regressions reported, each on a single arch,
which seemed to be unrelated to liburing; so just sent a
rerun request for them.
--
You received this bug notification because
TL;DR: giving it some time (tomorrow AM) for update_excuses to possibly
realize that mpd/samba/qemu deps are satisfiable (or for me to realize
i might be missing something; details below.)
---
liburing migrated after some autopkgtests/triggers tweaks.
plocate migrated.
mpd, samba, qemu are
Thanks for the info and the uploads.
That's good to know!
I didn't know it, and just added the bug reference in case it'd
be useful to find out why the no change rebuild was needed.
But I guess that can go in the changelog entry itself, right?
--
You received this bug notification because you
** Patch added: "lp1914145_qemu.debdiff"
https://bugs.launchpad.net/ubuntu/+source/liburing/+bug/1914145/+attachment/5459531/+files/lp1914145_qemu.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1914145_plocate.debdiff"
https://bugs.launchpad.net/ubuntu/+source/liburing/+bug/1914145/+attachment/5459530/+files/lp1914145_plocate.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1914145_mpd.debdiff"
https://bugs.launchpad.net/ubuntu/+source/liburing/+bug/1914145/+attachment/5459529/+files/lp1914145_mpd.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1914145_samba.debdiff"
https://bugs.launchpad.net/ubuntu/+source/liburing/+bug/1914145/+attachment/5459528/+files/lp1914145_samba.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Christian,
Attaching the debdiffs with no change rebuilds.
- samba is the most important, since it also fixes an autopkgtest
failure to unblock liburing in hirsute-proposed.
- mpd also has autopkgtests, but there's still a version in -proposed as
of now, so maybe it needs to wait (but since
liburing built successfully on all archs in hirsute-proposed.
autopkgtests look green (!) on amd64/arm64/ppc64el/s390x and
fail on armhf as seen previously (not a regression.)
autopkgtests for the reverse dependencies, in update_excuses:
- samba: fail consistently in all archs -- this is known
** Description changed:
New version (0.7-3) available without our delta (already forwarded
upstream), needs merge.
Reverse dependencies [2] need No-Change-Rebuilds to pick up the new ABI,
which unfortunately has been broken between 0.6-3 and 0.7-3 [3]:
- mpd, samba, plocate, qemu
** Description changed:
New version (0.7-3) available without our delta (already forwarded
upstream), needs merge.
Reverse dependencies [2] need No-Change-Rebuilds to pick up the new ABI,
- which unfortunately has been broken between 0.6-3 and 0.7-3 [3].
+ which unfortunately has been
nged in: qemu (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: samba (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: mpd (Ubuntu)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: plocate (Ubuntu)
Assignee: (unassigned) =>
Public bug reported:
New version available without our delta (already forwarded upstream),
needs merge.
** Affects: liburing (Ubuntu)
Importance: Wishlist
Assignee: Mauricio Faria de Oliveira (mfo)
Status: In Progress
** Changed in: liburing (Ubuntu)
Status: New
Hi Luka/@zapduke,
Can you test/verify bionic-proposed?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838152
Title:
gnome-shell freezes on notification arrival (fixed upstream)
To manage
** Changed in: librelp (Ubuntu Hirsute)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912969
Title:
librelp is FTBFS on riscv64 on Focal
Thanks again, Matthew.
I've reviewed and sponsored the new debdiff for Focal, with the existing
changes (so we have .20.04.1 and .2 in the same upload, going in focal-
proposed again.)
Further details added in bug 1912969.
--
You received this bug notification because you are a member of
Hi Matthew,
Can you please upload a debdiff for Hirsute as well?
I'll ask one of our core devs to handle it.
Thank you!
** Description changed:
[Impact]
During the recent SRU for bug 1908473, we found that librelp is FTBFS on
riscv64 on Focal, due to the test cases basic-realistic.sh
Reviewed and sponsored to Focal.
Per chat with Lukasz/sil2100 is is OK to have this only in Focal first,
but we'd like to see this in Hirsute, so that when we eventually (maybe
after Hirsute) re-enable the tests in riscv64, this is covered.
Thus marking Hirsute as In Progress, but this can be
Marking all other packages/dev release as Invalid.
Per previous discussion with Jay, iirc, those are
leftovers from a previously considered solution(s)
which was not the final one (in initramfs-tools.)
And just Bionic had to be patched as later releases
were not affected.
Please feel free to
@jibel done! sorry, I missed adding it earlier.
** Description changed:
+ [Impact]
+
+ * Currently ubiquity's prepare plugin, which installs the
+3rd party drivers, is not run at all in automatic mode.
+
+ * This prevents automatic installation of such drivers
+(e.g., nvidia
Hi Matthew,
Thanks for the analysis.
We'll need such changes on top of what's in -proposed (ie, in an
incremental version), re-uploaded.
Please see `dpkg-buildpackage -v` to generate a package build including
the version in -proposed plus the new version with the workaround for
the test-case.
** Tags removed: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898129
Title:
Cannot configure 'cryptsetup luksFormat' at install time
To manage notifications about this bug go to:
Hi Matthew,
I've kicked one or two rebuilds today, and still see the (same) one or
two tests failing.
I'm out this week so can't look much more into it (althogh I'm
admittedly curious about it :)
If you can take a look at these FTBFS test case failures, that would be
awesome; all archs must
The functionality is present in the desktop ISO daily build of
2021-01-21 [1] , per the ISO manifest file [2]:
ubiquity 20.04.15.3
It has been verified to work correctly on testing of that ISO, with the
following in a preseed file:
ubiquity partman-crypto/luksformat_options string \
** Also affects: ubiquity (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: ubiquity (Ubuntu Hirsute)
Importance: Medium
Assignee: Mauricio Faria de Oliveira (mfo)
Status: Fix Committed
** Changed in: ubiquity (Ubuntu Groovy)
Status: New => Wo
Now the two tests failed again.
I have to EOD, and this might benefit from some delay, in case the transient
condition just goes away.
Also, let's not overload the riscv64 builder with this so other builds can move
on.
We have 7 days in -proposed to look at this in more detail (or the bad
Same one failure, re-building again.
** Attachment added:
"buildlog_ubuntu-focal-riscv64.librelp_1.5.0-1ubuntu2.20.04.1_BUILDING.txt.gz.3"
and now it had only 1 failure in the test suite,
thus indeed a transient/arch-specific flakiness.
re-building once again.
$ zgrep '^FAIL: .*sh$'
buildlog_ubuntu-focal-riscv64.librelp_1.5.0-1ubuntu2.20.04.1_BUILDING.txt.gz.*
buildlog_ubuntu-focal-
focal/riscv64 had 2 failures in the test suite.
i've requested a re-build so it runs again, as
it seems more related to the arch or something
transient than the patchset, as only this arch
and release hit it.
(groovy: all archs ok, focal: other archs ok)
attaching build log for ref (it's lost on
** Patch added: "lp1908473_librelp_groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1908473/+attachment/5453105/+files/lp1908473_librelp_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1908473_librelp_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1908473/+attachment/5453106/+files/lp1908473_librelp_focal.debdiff
** Description changed:
[Impact]
In recent versions of rsyslog and librelp, the imrelp module leaks file
Matthew, thanks for the great work in this bug and patches.
Uploaded to Groovy and Focal w/ trivial changes; attached.
cheers,
Mauricio
...
debdiffs:
I've modified the patch files slightly, as we discussed;
- keep the commit messages;
- use its/patch headers for DEP3, adding Origin: /
Verification done for focal-proposed
---
All good, the package from -proposed works correctly in both scenarios
-- without the option (ie, default behavior) and with the option (ie,
opt-in behavior.)
Note: tested on VM with UEFI OVMF firmware with secure boot enabled
(OVMF_CODE_4M.ms.fd), as
** Patch added: "lp1898129_focal_ubiquity.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1898129/+attachment/5452745/+files/lp1898129_focal_ubiquity.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Verification done for focal-proposed (partman-crypto)
---
1) Booted the Ubuntu 20.04.1 Desktop ISO.
2) Launched a terminal, extracted the .udeb and copied over the crypto-base.sh
file.
3) Performed installation to encrypted disk without the preseed option
(default).
4) Performed installation to
Uploaded ubiquity to focal.
Two notes:
1) The 'debian/rules update' process picked up the new partman-crypto from
focal-proposed, and also shim-signed.
Discussed this with Laney and it shouldn't be an issue, as the ISO .list file
already shows the new version, so it's being used for a while
Based on good test results with partman-crypto (comment #19)
now moving on with ubiquity (to include the updated sources).
Tests with the patched packaged built from a PPA are positive.
The results are identical to the reported for partman-crypto
(LUKS2/LUKS1 by default/as requested; installed
** Tags added: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908473
Title:
rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which
leads to file descriptor leak
To
Uploaded partman-crypto to focal.
After it makes it to focal-proposed,
updated ubiquity upload will follow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898129
Title:
Cannot configure
** Patch added: "lp1898129_focal_partman-crypto.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1898129/+attachment/5450385/+files/lp1898129_focal_partman-crypto.debdiff
** Tags added: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
In order to fix this for Focal / 20.04.2 point release:
Groovy is a no-op, because:
1) it has no partman-crypto as stand-alone src pkg anymore.
2) its ubiquity (w/ bundled partman-crypto) doesn't need a
patch as there won't be new ISOs/Desktop install for it.
[thus, partman-crypto: Invalid /
Verification done for bionic-proposed.
The conntrack default ns and per-ns files for 'conntrack -L' and
'conntrack -S' are now present.
$ echo "deb http://archive.ubuntu.com/ubuntu $(lsb_release -cs)-proposed main
universe" \
| sudo tee /etc/apt/sources.list.d/proposed.list \
&& sudo
Verification done for groovy-proposed.
The conntrack default ns and per-ns files for 'conntrack -L' and
'conntrack -S' are now present.
$ echo "deb http://archive.ubuntu.com/ubuntu $(lsb_release -cs)-proposed main
universe" \
| sudo tee /etc/apt/sources.list.d/proposed.list \
&& sudo
Verification done for focal-proposed.
The conntrack default ns and per-ns files for 'conntrack -L' and
'conntrack -S' are now present.
$ echo "deb http://archive.ubuntu.com/ubuntu $(lsb_release -cs)-proposed main
universe" \
| sudo tee /etc/apt/sources.list.d/proposed.list \
&& sudo apt
Verification done for bionic-proposed.
The per-ns files for 'ip neigh' and 'ip rule' are now present.
$ echo "deb http://archive.ubuntu.com/ubuntu $(lsb_release -cs)-proposed main
universe" \
| sudo tee /etc/apt/sources.list.d/proposed.list \
&& sudo apt update \
&& sudo apt install
Verification done for focal-proposed.
The per-ns files for 'ip neigh' and 'ip rule' are now present.
$ echo "deb http://archive.ubuntu.com/ubuntu $(lsb_release -cs)-proposed main
universe" \
| sudo tee /etc/apt/sources.list.d/proposed.list \
&& sudo apt update \
&& sudo apt install
Verification done for groovy-proposed.
The per-ns files for 'ip neigh' and 'ip rule' are now present.
$ echo "deb http://archive.ubuntu.com/ubuntu $(lsb_release -cs)-proposed main
universe" \
| sudo tee /etc/apt/sources.list.d/proposed.list \
&& sudo apt update \
&& sudo apt install
>> +# Collect info from conntrackd
>
> This change seems to have disappeared in the backport to Bionic, but it
> doesn't matter so I left it.
Nice catch; I missed that one, sorry.
Thanks for the flexibility with that.
--
You received this bug notification because you are a member of
** Description changed:
+ [Impact]
+
+ * sosreport currently does not collect commands
+'ip neigh' and 'ip rule' for network namespaces,
+which are used with e.g., openstack neutron.
+
+ [Test Case]
+
+ * Create network namespace(s) (eg, ns1, ns2, ns3)
+$ sudo ip netns add ns1
+
** Description changed:
[Impact]
* The plugin conntrackd is renamed to conntrack.
+ (enabled automatically per installed packages.)
- * Added the following
- conntrack commands to the plugin.
- conntrack -L -o extended
- conntrack -S
+ * Added the following conntrack commands to the
** Tags removed: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820929
Title:
netplan should consider adding more udev attribute for exact matching
of failover 3-netdev interfaces
** Tags removed: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879980
Title:
Fail to boot with LUKS on top of RAID1 if the array is broken/degraded
To manage notifications about
Sponsored to F/G/B.
** Tags added: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898077
Title:
[conntrackd][plugin] add conntrack info
To manage notifications about this bug go
Sponsored to G/F/B.
** Tags removed: sts-sponsor-volunteer
** Tags added: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901555
Title:
[plugin][networking] Include ns ip neigh and
Verification for test packages on Bionic.
===
$ sudo ip netns add ns1
$ sudo ip netns add ns2
$ sudo ip netns add ns3
$ ip netns
ns3
ns2
ns1
$ sudo apt install conntrack conntrackd
$ lsb_release -cs
bionic
Before: (no conntrack files; only conntrackd)
---
$ dpkg -s sosreport | grep -i
Verification for test packages on Focal.
===
$ sudo ip netns add ns1
$ sudo ip netns add ns2
$ sudo ip netns add ns3
$ ip netns
ns3
ns2
ns1
$ sudo apt install conntrack conntrackd
$ lsb_release -cs
focal
Before: (no conntrack files; only conntrackd)
---
$ dpkg -s sosreport | grep -i
Verification for test packages on Groovy.
===
$ sudo ip netns add ns1
$ sudo ip netns add ns2
$ sudo ip netns add ns3
$ ip netns
ns3
ns2
ns1
$ sudo apt install conntrack conntrackd
$ lsb_release -cs
groovy
Before: (no conntrack files; only conntrackd)
--
$ dpkg -s sosreport | grep -i
Packages built successfully for all architectures on
ppa:mfo/lp1898077-lp1901555.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898077
Title:
[conntrackd][plugin] add conntrack info
To manage
Verification for test packages on Bionic.
===
$ sudo ip netns add ns1
$ sudo ip netns add ns2
$ sudo ip netns add ns3
$ ip netns
ns3
ns2
ns1
$ lsb_release -cs
bionic
Before: (no files for ip neigh/rule per network namespace)
---
$ dpkg -s sosreport | grep -i version:
Version:
Verification for test packages on Groovy.
===
$ sudo ip netns add ns1
$ sudo ip netns add ns2
$ sudo ip netns add ns3
$ ip netns
ns3
ns2
ns1
$ lsb_release -cs
groovy
Before: (no files for ip neigh/rule per network namespace)
--
$ dpkg -s sosreport | grep -i version:
Version: 4.0-1ubuntu2
Verification for test packages on Focal.
===
$ sudo ip netns add ns1
$ sudo ip netns add ns2
$ sudo ip netns add ns3
$ ip netns
ns3
ns2
ns1
$ lsb_release -cs
focal
Before: (no files for ip neigh/rule per network namespace)
---
$ dpkg -s sosreport | grep -i version:
Version:
This patch is being sponsored/uploaded for stable releases via bug
1898077.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901555
Title:
[plugin][networking] Include ns ip neigh and ip rule info
** Changed in: sosreport (Ubuntu Groovy)
Assignee: Hemanth Nakkina (hemanth-n) => Mauricio Faria de Oliveira (mfo)
** Changed in: sosreport (Ubuntu Focal)
Assignee: Hemanth Nakkina (hemanth-n) => Mauricio Faria de Oliveira (mfo)
** Changed in: sosreport (Ubuntu Bionic)
As
** Changed in: sosreport (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: sosreport (Ubuntu Groovy)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: sosreport (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: sosreport (Ubu
** Patch added: "lp1898077_lp1901555_sosreport_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1898077/+attachment/5447752/+files/lp1898077_lp1901555_sosreport_bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Patch added: "lp1898077_lp1901555_sosreport_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1898077/+attachment/5447751/+files/lp1898077_lp1901555_sosreport_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Patch added: "lp1898077_lp1901555_sosreport_groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1898077/+attachment/5447750/+files/lp1898077_lp1901555_sosreport_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Attaching updated debdiffs that include bug 1901555.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898077
Title:
[conntrackd][plugin] add conntrack info
To manage notifications about this bug go
Hi Petar,
Thanks for letting us know, and sorry it wasn't possible to get back to
this bug.
I'll mark it as Invalid as the root cause isn't know; but glad it's
working now.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are
Next Steps:
1) Upload partman-crypto to focal.
2) Wait for it to be available in focal-proposed.
3) Upload ubiquity to focal (gets focal-proposed.)
We could upload both and coordinate the time that
they are accepted and published (ubiquity must be
after partman-crypto), but plans might go wrong
All looks good with the PPA build.
After patch/build partman-crypto, and updating its sources
in ubiquity (adding an apt source to the PPA, of course),
the ubiquitu .deb package includes the partman-crypto changes
in '/lib/partman/lib/crypto-base.sh' as expected.
--
You received this bug
Actually, step 2) is not a no-change-rebuild, but running 'debian/rules
update', which adds to the changelog properly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898129
Title:
Cannot configure
Actually in Focal partman-crypto is present in ubiquity
(in d-i/source/partman-crypto) so we'll change it again.
However, ubiquity in Focal doesn't yet use git subtrees;
it just `apt-get source` the d-i components, so we need:
1) patch partman-crypto/focal.
2) no-change-rebuild ubiquity/focal,
** Changed in: ubiquity (Ubuntu Focal)
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898129
Title:
Cannot configure 'cryptsetup luksFormat' at install time
Hi Pon,
Thanks for clarifying offline that the Openstack/Ceph team is okay with
more than one commit per patch file.
So, on the debdiff 'noise', I've previously seen and usually removed
that stuff; this seems to be due to the packaging not cleaning up files
generated at build time, I guess.
You
In order to fix this in Focal for the 20.04.3 point release:
Groovy is a no-op, since it has no partman-crypto, and its
ubiquity doesn't need the patch as there won't be new ISOs.
[thus: partman-crypto / Invalid; ubiquity / Won't Fix.]
Focal needs the patch on partman-crypto only (as it is not
This has been fixed on Hirsute; changing to Fix Released.
"""
ubiquity (21.04.3) hirsute; urgency=medium
[ Mauricio Faria de Oliveira ]
* Introduce preseed option partman-crypto/luksformat_options
[ Łukasz 'sil2100' Zemczak ]
* Automatic update of included source pa
301 - 400 of 1696 matches
Mail list logo
