Autopkgtests are now clear in update_excuses and pending-sru.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/2033892
Title:
ls -l triggers mount of autofs shares when
For dotnet6 on amd64 and arm64, the errors are unrelated to coreutils
(the same test errors happen against dotnet6 itself and even glibc),
thus triggered a migration-reference/0 run.
[0,3] trigger: coreutils/8.32-4.1ubuntu1.2
dotnet-runtime-json-contains-ubuntu-rids FAIL non-zero exit
Re: comment #15
> autopkgtest for dotnet6/6.0.128-0ubuntu1~22.04.1: amd64: Regression ♻ ,
> arm64: Regression ♻
> autopkgtest for linux-hwe-5.19/5.19.0-50.50: amd64: Pass, arm64: Regression ♻
> , ...
> autopkgtest for linux-hwe-6.5/6.5.0-27.28~22.04.1: arm64: Regression ♻ , ...
dotnet6 amd64
No problem, Mitchell!
Yes, the point pending from comment #44 (.3) is resolved for Jammy per
#48 (so Jammy should be OK, AFAICT), and pending for Focal per #49
(being addressed per #50; thanks!).
Please note that other SRU vanguards may have a different opinion (or
raise other points I may have
Hi Mitchell,
Indeed, there are some autopkgtests results/failures that are not
reported in pending-sru or update_excuses -- this is the case specially
for Focal (Jammy looks good).
I downloaded the autopkgtest.db from autopkgtest.ubuntu.com, and locally
queried it.
The test results with
RELEASE=jammy
TRIGGER=python2.7/2.7.18-13ubuntu1.2
sqlite3 autopkgtest.db -column -header \
"SELECT test.release, test.arch, test.package, "\
" result.version, result.exitcode, "\
" result.triggers, result.requester "\
"FROM test, result "\
"WHERE test.id = result.test_id "\
"AND
RELEASE=focal
TRIGGER=python2.7/2.7.18-1~20.04.4
sqlite3 autopkgtest.db -column -header \
"SELECT test.release, test.arch, test.package, "\
" result.version, result.exitcode, "\
" result.triggers, result.requester "\
"FROM test, result "\
"WHERE test.id = result.test_id "\
"AND
Hey Mitchell,
No, the autopkgtests re-run for python2.7/focal are done and OK ('they continue
to fail').
Link: [1] (see the Focal results on diff archs have 'migration-reference/0' and
'mfo').
The autopkgtests point pending is a clarification on the
database/results, ie, whether we can trust
Just a few observations before release.
1) The verification for Jammy apparently has a copy-paste error,
as the banner about the env var is present (step 5) _before_ the
package from -proposed -- which adds it -- is installed (step 6).
To be clear, this is not a problem and should not block the
> Apologies, I saw the same issue locally fixed it but must have
forgotten to build a new .dsc:/
No worries; thanks for mentioning!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
Hello Åka, or anyone else affected,
Accepted debootstrap into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/debootstrap/1.0.118ubuntu1.13 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
The changes for Focal had a syntax error (double ';;' lines, not present
in Jammy) which causes debootstrap to fail early and silently, even for
a previously working series.
Original:
$ sudo debootstrap --variant=minbase focal /tmp/debootstrap.focal
http://br.archive.ubuntu.com/ubuntu
Testing with the change applied:
$ sudo debootstrap --variant=minbase noble /tmp/debootstrap.noble
http://br.archive.ubuntu.com/ubuntu
...
I: Base system installed successfully.
$ echo $?
0
$ ls -l /tmp/debootstrap.noble/ | grep usr/
Considerations for the SRU team:
I confirmed that the behavior in Jammy is different than
Focal and Mantic, the previous / next supported releases.
(Steps in the next comment.)
So, although this SRU changes behavior in a stable release
(generally not OK in SRUs), it is actually Jammy that
Reviewed and sponsored to Jammy; thanks!
Notes:
- Please add test for `stat` as well (bottom of tests comment).
- I just changed the DEP3 Origin tag (commit ID; backport_ed_).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Test Steps:
lxc launch --vm ubuntu:$SERIES autofs-$SERIES
lxc shell autofs-$SERIES
# replace linux-kvm with linux-generic for autofs
DEBIAN_FRONTEND=noninteractive apt remove --yes --purge
** Tags removed: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/2033892
Title:
ls -l triggers mount of autofs shares when --ghost option is present
or
Hello Åka, or anyone else affected,
Accepted debootstrap into jammy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/debootstrap/1.0.126+nmu1ubuntu0.7
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
I confirmed that the resulting target dir of debootstrap in Jammy (with
patch/MERGED_USR=no) and Mantic is the same, with a comparison of `ls
-lR` (normalized for Month/Day/Time fields).
...
Test command for Jammy (patched) and Mantic:
# debootstrap --arch=amd64 --variant=minbase --keyring
TL;DR: The fix is not needed on Mantic.
This is just to expand a bit on the brief note in '[Where problems could
occur]' ("moved to merging post-extraction"), for clarity.
The code in `scripts/gutsy` (used for noble) is different between Mantic
and Jammy with regards to the order of package
PS: the Jammy verification done in comment 31 used version
2.37.2-4ubuntu3.1 (staged in this bug), and that in comment 39 used
(newer) version 2.37.2-4ubuntu3.2 (also staged, in bug 2048092) -- both
have positive results.
BTW, since the newer upload is still planned for staging, not removing
the
Jammy verification done in comments 31 (with tag flip) and 39.
Lunar is now Won't Fix (2024-01-17), thus removing lunar tags.
** Tags removed: block-proposed-lunar verification-done-lunar
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Notes:
- Added bug task for Lunar (lunar MR is linked/approved; lunar-unapproved has
an upload).
- Checked that Bionic and Xenial have no conflicting packages/versions in the
ESM archive.
** Also affects: base-files (Ubuntu Lunar)
Importance: Undecided
Status: New
** Changed in:
Verification done on mantic-proposed.
On arm64 with ubuntu-desktop-minimal installed,
running do-release-upgrade from lunar to mantic
(with mantic-proposed enabled and pinning setup)
does install `protection-domain-mapper` and
`qrtr-tools` (`flash-kernel` already installed).
Test Steps:
---
Verification (synthetic) of the XDG_SESSION_TYPE fix in Mantic:
$ lsb_release -cs
No LSB modules are available.
mantic
The packages are downloaded from Launchpad librarian
since previous versions are not available in archive.
Before the fix (reverted) // 1:23.10.12
---
Summary for Mantic SRUs.
There are 3 LP bugs combined in mantic-proposed
(list sorted by package version so it's helpful).
1) Bug 2034986, used twice,
1A) First for 1:23.10.9, for 'fix v1':
* Temporary font for Ubuntu MATE (LP: #2034986)
It's released to mantic-updates with 1:23.10.10
** Changed in: ubuntu-meta (Ubuntu Noble)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2039328
Title:
Update ubuntu-meta
** Description changed:
[ Impact ]
* ubuntu-seeds were changed since last meta update
* to ensure correct upgrades; regenerate ubuntu-meta with contents / changes
done before release
[ Test Plan ]
* Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to
mantic
Updated regression potential with theoretical issues, and other info
with status in main for protection-domain-mapper and qrtr.
** Description changed:
[ Impact ]
- * ubuntu-seeds were changed since last meta update
- * to ensure correct upgrades; regenerate ubuntu-meta with contents /
(unassigned) => Mauricio Faria de Oliveira (mfo)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2039328
Title:
Update ubuntu-meta with promotions done between last ub
** Changed in: ubuntu-pro/18.04
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2038453
Title:
[SRU] apt snapshot integration backport
Status in
** Also affects: apt (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu Bionic)
Status: New => Won't Fix
** Also affects: ubuntu-pro
Importance: Undecided
Status: New
** Also affects: ubuntu-pro/18.04
Importance: Undecided
Status:
All autopkgtests have now passed (lunar/jammy).
https://ubuntu-archive-team.ubuntu.com/proposed-migration/lunar/update_excuses.html#util-linux
https://ubuntu-archive-team.ubuntu.com/proposed-migration/jammy/update_excuses.html#util-linux
--
You received this bug notification because you are a
The autopkgtests failures in lunar seem to be a kernel issue during the
initialization of the virtio rng driver, when the mutex for
(generic/core) hw rng is acquired (apparently something else is holding
it indefinitely, thus the blocked task warnings show up, and it seems
the VM doesn't proceed
The autopkgtests failures in jammy seem to be of various sorts, but are
not expected to be related to this code change at all. I've skimmed
through them, and some seemed worth of retries (timeouts, network
issues, etc).
--
You received this bug notification because you are a member of Ubuntu
Thanks for reporting this bug!
Could not reproduce with Kinetic (22.10) or Lunar (23.04).
Kinetic will EOL soon. Can you reproduce this with Lunar?
Thanks!
$ lsb_release -cs
No LSB modules are available.
lunar
$ uuidgen -t
039c7806-20ae-11ee-ba46-54e1ad759c00
...
$ lsb_release -cs
kinetic
The problem does not seem to be in util-linux, as it works correctly
with a loop device.
Can you confirm whether you have /dev/disk/by-label/ symlinks for the
new filesystem?
$ lsb_release -cs
jammy
$ truncate -s 15T disk.img
$ DEV=$(sudo losetup --find --show disk.img)
$ sudo mkfs.btrfs -O
Steve / #17,
Sorry, this was discussed internally at the time, but for some reason
the answers didn't make it here back then.
If we get another bug (e.g., another simple change from existing util-
linux bugs, that still makes sense to be SRUed) that can be combined
with this SRU, would that be
Uploaded to Lunar and Jammy, but not Kinetic (Won't Fix).
$ ubuntu-distro-info --series=kinetic --days=eol
45
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
util-linux 2.38.1-5ubuntu1 finally migrated from mantic-proposed to mantic
(its autopkgtests were very slow/cycling last week, apparently).
I'll check for potential sponsors to the debdiff in comment #10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
For Mantic, this indeed requires a patch, not a merge/sync, as Debian
doesn't have the commit yet either.
$ git remote get-url origin
git://git.kernel.org/pub/scm/utils/util-linux/util-linux.git
$ git describe --contains 6857cccbb4157d5da34ca98f77a0ac9d68e1e740
v2.39-rc1~126^2~4
$ git show
Debdiff on top of mantic-proposed (2.38.1-5ubuntu1), which should
migrate soon (all good on update-excuses [1] / pending autopkgtests).
https://people.canonical.com/~ubuntu-archive/proposed-
migration/update_excuses.html#util-linux
** Patch added: "lp2019856-mantic-util-linux.debdiff"
Test packages in ppa:mfo/lp2019856, verified with GDB
(to fake CPU IDs) on Google Cloud ARM-based instances.
No differences in `lscpu` output for non-affected CPU.
Expected output for both affected CPUs (0xd15, 0xd4f).
Tested on LXD containers for Mantic, Lunar, and Jammy
(not on Kinetic as it
Hey Heather, thanks for the updated debdiffs!
I've looked at them, and did minor fixes to DEP3
(moved them out of the original commit message,
after `---`, and added Origin: fields), and just
a cosmetic adjustment to the changelog.
It turns out this patch isn't present in Mantic.
I already
** Description changed:
[Impact]
- When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't
report a model name:
+
+ When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't
+ report a model name:
Vendor ID: ARM
Model: 0
[Fix]
- Adding the additional
tic)
Status: New => In Progress
** Changed in: util-linux (Ubuntu Mantic)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Tags removed: verification-needed-jammy verification-needed-lunar
--
You received this bug notification because you are a member of Ubuntu
Tou
Heather mentioned some changes she has for the debdiffs, I also noted
some changes to DEP3 headers, and debdiffs v2 are in progress. Thanks,
Heather!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
** Tags added: se-sponsor-mfo
--
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/2019856
Title:
Add missing ARM-cores to support Grace-based systems
Status in util-linux
The fix/commit is applied in v5.12, thus available on Jammy
(v5.15-based).
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4ceddce55eb35d15b0f87f5dcf6f0058fd15d3a4
~/git/linux$ git describe --contains 4ceddce55eb35d15b0f87f5dcf6f0058fd15d3a4
Marking bug as Invalid for MAAS as per previous comment, incomplete
status since, and input from Björn and Jerzy.
** Changed in: maas
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Tags added: se-00140843
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1677668
Title:
no GARPs during ephemeral boot
Status in MAAS:
Incomplete
Status in
Hey Simon. Understood, thanks for the clarification!
--
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/2009699
Title:
sytemd-udev package upgrade breaks if udev is masked
Hi Simon,
Thanks for the detailed report!
For testing purposes, this can be reproduced this with standard LXD
images by masking the systemd-udev.service unit, as you described.
Could you please confirm if from the Anbox perspective, for a
workaround, is it OK to temporatily unmask/start the
Verification done on focal
(full steps on comment #13)
$ lxc shell focal-dhcpd
# add-apt-repository -y 'deb http://archive.ubuntu.com/ubuntu focal-
proposed main'
root@focal-dhcpd:~# apt policy isc-dhcp-client
isc-dhcp-client:
Installed: 4.4.1-2.1ubuntu5.20.04.4
Candidate:
Verification done on jammy
(full steps on comment #12)
$ lxc shell jammy-dhcpd
# add-apt-repository -yp proposed
# apt policy isc-dhcp-client
isc-dhcp-client:
Installed: 4.4.1-2.3ubuntu2.3
Candidate: 4.4.1-2.3ubuntu2.4
Version table:
4.4.1-2.3ubuntu2.4 500
500
The -proposed packages have also been verified by the Microsoft Azure team.
14k+ VM deployments with the fix didn't observe the issue over the weekend.
Marking jammy/focal as verified based on that plus 2 synthetic tests
above.
** Tags removed: verification-needed verification-needed-focal
verification done on focal
(full steps in comment #9)
The issue is not reproducible with the package in -proposed,
and is reproducible with the 2 switches for the old behavior
(DHCP_FD_FLAGS_POKE=0 or dhcp.fd_flags_poke=0), as expected.
...
# add-apt-repository -y 'deb
verification done on jammy
(full steps in comment #9)
The issue is not reproducible with the package in -proposed,
and is reproducible with the 2 switches for the old behavior
(DHCP_FD_FLAGS_POKE=0 or dhcp.fd_flags_poke=0), as expected.
...
# add-apt-repository -yp proposed
# apt policy
** Tags added: se-sru-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1926139
Title:
dhclient: thread concurrency race leads to DHCPOFFER packets not being
Uploaded to Jammy/Focal.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1937110
Title:
dhcp option 121 & 249
Status in subiquity:
New
Status in isc-dhcp package in
Reproducer with DHCP server/client on LXD. [Focal]
Bridge
---
sudo ip link add focalbr type bridge
sudo ip link set focalbr up
LXD container for DHCP server with classless static routes option
---
lxc init ubuntu:focal focal-dhcpd
lxc config device add
ded => Medium
** Changed in: isc-dhcp (Ubuntu Focal)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: isc-dhcp (Ubuntu Jammy)
Status: Incomplete => In Progress
** Changed in: isc-dhcp (Ubuntu Jammy)
Importance: High => Medium
--
You received this b
>From the 'Where problems could occur' section.
Considerations on regressions and approaches.
[Where problems could occur]
isc-dhcp is a core package, and any change comes with the risk that
users would not be able to receive dhcp leases with dhclient, leaving
their systems with no IP address
From the 'Other Info' section.
Detailed analysis of the issue and more.
[Other Info]
Full log: https://paste.ubuntu.com/p/8yBfw2KR5h/
Log of a working run: https://paste.ubuntu.com/p/N3ZgqrxyQD/
When you tcpdump dhclient, we see all DHCPDISCOVER packets being replied
to with DHCPOFFER packets,
Pressing Page Down 17 times to go over the bug description sounds like a
new record! ;-)
Just in case future reviewers don't find that as exciting while going
through reviews, I'll move some text into comments and reference them
from the description.
** Bug watch added:
Jammy/22.04:
- test packages in ppa:mfo/lp1926139
- reproduction steps delta (based on comment #9)
...
Reproducer based on GDB and DHCP noise injection.
It uses 3 veth pairs (DHCP server/client/injector,
the latter two under namespaces) on a linux bridge.
...
LXD VM:
lxc launch ubuntu:jammy
** Patch added: "lp1926139_focal_isc-dhcp_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5643626/+files/lp1926139_focal_isc-dhcp_v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Test packages:
https://launchpad.net/~mfo/+archive/ubuntu/lp1926139
isc-dhcp 4.4.1-2.1ubuntu5.20.04.4+lp1926139.2
Default behavior: issue fixed.
---
(gdb) break omapip/dispatch.c:333
(gdb) commands
shell sleep 0.2
continue
end
(gdb) run -d -v
Hey Matthew, Chris,
Apparently there's a simpler, less intrusive, and more specific way to
do this.
Apologies that I missed this earlier, but I found more about the
possibilities in bind9-libs functions while checking the previous fix
approach for regressions.
Could you please provide your
For documentation purposes.
The autopkgtests failures for systemd were unrelated to this
(not regressions).
I checked their logs and reran with the migration-reference/0
trigger so not to use kbd from -proposed; that failed as well.
The pending SRU and update-excuses pages no longer show kbd
** Patch added: "lp1926139_focal_isc-dhcp.debdiff"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5642442/+files/lp1926139_focal_isc-dhcp.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Hi Matthew,
Thanks for the excellent analysis and considerate fix proposal, as
always!
I looked at this for the last couple of days, for potential sponsorship.
I have attentively gone through the SRU template and Other Info section,
and considered the proposal to switch bind9-libs into
Reproducer based on GDB and DHCP noise injection.
It uses 3 veth pairs (DHCP server/client/injector,
the latter two under namespaces) on a linux bridge.
LXD VM:
$ lxc launch ubuntu:focal lp1926139-focal --vm
$ lxc shell lp1926139-focal
Network Setup:
# ip link add br0
** Tags removed: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1926139
Title:
dhclient: thread concurrency race leads to DHCPOFFER packets not being
Hi. No, I haven't tested on that; but if this helps, the issue is
independent of platform/hypervisor as it's in ufw/firewall, thus the fix
should help anyway.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
Thanks, Heather!
Uploaded to Kinetic and Jammy (minor adjustments; build tested on supported
archs w/ -proposed).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kbd in Ubuntu.
https://bugs.launchpad.net/bugs/1996619
ntu Bionic)
Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned)
--
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/1996958
Title:
[Azure] 18.04 - non-unique I
** Patch added: "lp1996958-bionic-systemd.debdiff"
https://bugs.launchpad.net/ubuntu/bionic/+source/systemd/+bug/1996958/+attachment/5635743/+files/lp1996958-bionic-systemd.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: lvm2 (Ubuntu Focal)
Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned)
** Tags removed: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.
Heather and I internally discussed some feedback/review for the revised
debdiffs.
** Tags removed: sts-sponsor
** Tags added: se-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kbd in Ubuntu.
Scenario 2) LUN numbers 0, 1, and 5 (non-0/1 test).
$ dmesg | grep Hypervisor
[0.00] Hypervisor detected: Microsoft Hyper-V
$ uname -r
5.4.0-1094-azure
$ lsscsi | grep sd
[0:0:0:0]diskMsft Virtual Disk 1.0
Scenario 1) LUN numbers 0 and 1 only.
$ dmesg | grep Hypervisor
[0.00] Hypervisor detected: Microsoft Hyper-V
$ uname -r
5.4.0-1094-azure
$ lsscsi | grep sd
[0:0:0:0]diskMsft Virtual Disk 1.0 /dev/sdc
[0:0:0:1]
Test packages on ppa:mfo/lp1996958 [1].
Initial tests show positive results (next comments).
Waiting on feedback from the original reporter.
[1] https://launchpad.net/~mfo/+archive/ubuntu/lp1996958
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I have verified the scenario that Seyeong mentioned
where the patch apparently dit not make a difference
(SCSI disks with LUN numbers greater than 1, eg, 5).
My observation is it indeed works/makes a difference.
He went out on vacation (so I'm reassigning the bug), and
cannot confirm this, but
disks
** Changed in: systemd (Ubuntu Bionic)
Assignee: Seyeong Kim (seyeongkim) => Mauricio Faria de Oliveira (mfo)
--
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/19969
** Description changed:
[Impact]
Azure 18.04 has issue with /dev/disk/by-path/ has the same path name when vm
has multiple disks.
[Test Plan]
1. launch 18.04 on azure
2. add extra disk to #1 vm
3. check the path
xtrusia@test-canonical:~$ udevadm info --name=/dev/sda | grep
** Description changed:
[Impact]
Azure 18.04 has issue with /dev/disk/by-path/ has the same path name when vm
has multiple disks.
[Test Plan]
1. launch 18.04 on azure
2. add extra disk to #1 vm
3. check the path
xtrusia@test-canonical:~$ udevadm info --name=/dev/sda | grep
Ah, you might want to do systemd first, if a reboot isn't desirable.
If a reboot is fine, then maybe also just check again after reboot,
in case it's a transient system condition unrelated to the upgrades.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
> ... from systemd 237-3ubuntu10.53 to 237-3ubuntu10.56
> and are experiencing some performance issues.
> A kernel upgrade also happened (4.15.0.192.177 -> 4.15.0.193.178)
> but I thought I'd check here first.
> Sorry if I'm raising this in the wrong place!
Thanks for the bug report!
No
Hey Jeremy,
Understood; thanks for clarifying!
I thought that maybe having upstream input could be helpful
(as Julian mentioned to avoid diverging further), but if it
is so much different nowadays, as you mentioned, it likely
won't be that helpful anyway.
By the way, appreciate that "newbie"
Hi Jeremy,
It seems the PR in rhboot's grub2 hasn't been reviewed yet;
just mentions from other folks who also found it helpful.
Would you consider sending this to the grub-devel list? (i.e., upstream gnu's
grub2)
It looks like it wasn't yet (search results only cover rhboot).
By the way, this
Nicolas and I talked about a brief review of the debdiff,
and he kindly agreed to provide an update/v2 to address:
- changelog version and description line
- patches dep3 headers and lpnumber- prefix
... while patches are reviewed for feedback (not yet done).
Thanks, Nicolas!
--
You received
Update: this has been fixed in Focal (same fix commit):
openssl (1.1.1f-1ubuntu2.11) focal; urgency=medium
* Fixup pointer authentication for armv8 systems that support it when
using the poly1305 MAC, preventing segmentation faults. (LP: #1960863)
-
Setting verification-done-bionic per comments 39/40.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Verification done on focal-proposed; all good.
Host:
---
$ sudo dd if=/dev/sda of=/dev/null
dd: failed to open '/dev/sda': No medium found
$ lxc launch ubuntu:focal lp1834250
$ lxc config device add lp1834250 host-sda unix-block source=/dev/sda
path=/dev/sda
** Patch added: "lp1834250_lvm2_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1834250/+attachment/5593897/+files/lp1834250_lvm2_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in
Uploaded to Focal, and tagged block-proposed-focal.
Attaching slightly modified debdiff (local build version),
for users who want to build lvm2 before a SRU is released.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2
** Description changed:
[Impact]
* `update-grub` (actually `vgs`) complains about
'No medium found' on systems with card readers
that have no card in.
* This may confuse users who aren't sure whether
it means problems occurred with the bootloader,
and concern
Setup:
--
Add '/dev/sda' from the host to a Focal LXD container:
$ lxc launch ubuntu:focal 'focal-container'
$ lxc config device add 'focal-container' 'lxc-dev-sda' unix-block
source='/dev/sda' path='/dev/sda'
Device:
---
$ grep ^
* Changed in: lvm2 (Ubuntu Focal)
Importance: Undecided => Low
** Changed in: lvm2 (Ubuntu Focal)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Tags added: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
1 - 100 of 384 matches
Mail list logo
