** Changed in: ksh93u+m (Ubuntu Jammy)
Assignee: Heitor Alves de Siqueira (halves) => (unassigned)
** Changed in: ksh93u+m (Ubuntu Noble)
Assignee: Heitor Alves de Siqueira (halves) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
I've validated this on the original reproducer system, and confirm the
ns-stress.sh script does not reproduce the error anymore.
# uname -rv
6.8.0-72-generic #72-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 23 11:57:52 UTC 2025
** Tags removed: verification-needed-noble-linux
** Tags added: verification-do
We've had an OOB sync w/ Simon and Ioanna, and it was agreed to let this
one be sponsored separately from Simon's usual glibc uploads.
@joalif: your debdiff looks good overall, thanks! Given this is fixing
cross-compilation for both i386 and m68k, could you add that second arch
into the test plan?
This is a bug against glibc, so I've marked the zsh targets as Invalid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2036283
Title:
i386 glibc is missing fmod in libm.a
To manage notifications abo
** Description changed:
- [Description]
- The `libm.a` static library on i386 architecture lacks the math function
`fmod`:
+ [Impact]
+ The `libm.a` static library on i386 architecture lacks the math function
`fmod`. This will break static compilation in scenarios where programs expect
the func
** Changed in: zsh (Ubuntu Noble)
Status: Confirmed => Invalid
** Changed in: zsh (Ubuntu)
Status: Confirmed => Invalid
** Changed in: glibc (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: glibc (Ubuntu Noble)
Status: Confirmed => In Progress
** Changed in:
** Changed in: pipewire (Ubuntu Questing)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100497
Title:
Duplicated audio sample played after silence
To m
I've opened bug 2117103 for tracking this, and will upload the fixes
soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2110614
Title:
[SRU] Honour attributes for local assignments in subshells
To
ll have to be
extra careful on any future syncs to not re-introduce breakage.
** Affects: ksh93u+m (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: ksh93u+m (Ubuntu Jammy)
Importance: Low
Assignee: Heitor Alves de Siqueira (halves)
Status: I
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2020139
Title:
[SRU] Image fetch speed from Glance to Cinder volume service can be
** Changed in: nova (Ubuntu)
Status: New => Fix Released
** Changed in: nova (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: nova (Ubuntu Jammy)
Status: New => In Progress
** Changed in: nova (Ubuntu Jammy)
Assignee: (unassigned) => Edward Hope-Morley (hopem)
** Description changed:
[Impact]
The fix in bug 2091033 led to a regression that is fixed by this patch.
In order to backport the former we also need this patch so both are
being proposed for SRU at the same time.
[Test Plan]
- * Deploy Openstack Yoga and ensure that "TypeError
ACK, thanks for clearing that up Alessandro!
Unfortunately for the purpose of validation, I've actually rebooted the
instance completely to make sure there were no left-over services using
the old version. I'm hesitant to mark this as verification-failed as
this is a headless server, so maybe I'm
Hi folks,
I've attempted to verify this on an arm64 server running noble, but I've
been unable to understand what's different when using the Test Plan from
the description with packagekit from noble-proposed. When I run the
pkcon queries for 64bit, I get empty outputs:
ubuntu@noble-arm64:~$ pkcon
I've redeployed the original server, and re-tested this with Jammy. I
left the script running for a couple of days, and actually managed to
fill up the ZFS storage without running into the object number issues.
ubuntu@wringer-wooster:~$ zfs version
zfs-2.1.5-1ubuntu6~22.04.6
zfs-kmod-2.1.5-1ubuntu
** Changed in: openvswitch (Ubuntu Plucky)
Status: New => In Progress
** Changed in: openvswitch (Ubuntu Questing)
Status: New => In Progress
** Changed in: openvswitch (Ubuntu Plucky)
Assignee: (unassigned) => Arif Ali (arif-ali)
** Changed in: openvswitch (Ubuntu Questing)
I'm marking Oracular as Won't Fix, as it's going to be EOL before the
next kernel cycle completes.
** Also affects: linux (Ubuntu Plucky)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Questing)
Importance: Medium
Status: Fix Released
** Also affects: linux
** Description changed:
[Impact]
During repeated NS map/unmap operations in ONTAP (which triggers NS attr
changed AENs) where new NSs get mapped reusing the old NSID, one occasionally
sees the Ubuntu 24.04 NVMe/TCP host ending up with device inconsistencies where
the respective NVMe block d
** Description changed:
[Impact]
During repeated NS map/unmap operations in ONTAP (which triggers NS attr
changed AENs) where new NSs get mapped reusing the old NSID, one occasionally
sees the Ubuntu 24.04 NVMe/TCP host ending up with device inconsistencies where
the respective NVMe block d
** Attachment added: "zfs_write_unified.py"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2115683/+attachment/5887793/+files/zfs_write_unified.py
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
I've validated this on noble using the same server as before, since I
had a zpool snapshot that reliably reproduces this issue. I left the
zfs_write_unified.py script running for around an hour, and everything
looks good. No hangs or kernel spews were detected.
ubuntu@wringer-wooster:~$ apt policy
Validated on a Jammy VM with the HWE kernel, according to the Test Plan
from the description. With arc_summary from jammy-proposed, everything
works correctly on both the GA and HWE kernels:
root@halves-jammy:~# apt policy zfsutils-linux
zfsutils-linux:
Installed: 2.1.5-1ubuntu6~22.04.6
Candi
** Tags removed: verification-done
** Tags added: verification-needed verification-needed-jamm
** Tags removed: verification-needed-jamm
** Tags added: verification-needed-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Merge proposal linked:
https://code.launchpad.net/~halves/ubuntu/+source/nova/+git/nova/+merge/488231
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1984736
Title:
[SRU]"TypeError: catching cl
** Merge proposal linked:
https://code.launchpad.net/~halves/ubuntu/+source/nova/+git/nova/+merge/488232
** Merge proposal unlinked:
https://code.launchpad.net/~hopem/ubuntu/+source/nova/+git/nova/+merge/488177
** Merge proposal unlinked:
https://code.launchpad.net/~hopem/ubuntu/+source
** Merge proposal linked:
https://code.launchpad.net/~halves/ubuntu/+source/nova/+git/nova/+merge/488232
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054446
Title:
[SRU] Boot from ISO does not
** Tags added: verification-needed verification-needed-noble
verification-needed-oracular verification-needed-plucky
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2111723
Title:
lscpu wrong core rep
@pho that's great news, thanks for confirming!
On your question about the modules, these are typically picked-up at
build time for the kernel packages. We typically expect the new ZFS
version to be available in linux-modules in the next kernel release [0]
(i.e. mid July).
[0] https://kernel.ubunt
been upstream since May/2024, and is included with ZFS releases
starting with 2.2.5. As such, Jammy and Noble are affected, and releases
starting with Oracular already have this fix.
** Affects: zfs-linux (Ubuntu)
Importance: High
Assignee: Heitor Alves de Siqueira (halves)
Hi Luciano,
I've noticed that the verification for Oracular has been done against
the builds from your PPA. Unfortunately, for SRU purposes this must be
done with packages from proposed. I'm setting the tags back, and would
appreciate it if we could rerun validation against the current packages
fr
Hi all,
thanks for the fixes! From a cursory look at the source for Jammy [0],
this still seems broken there. Is there a need to get this fix into
older releases as well?
[0]
https://git.launchpad.net/ubuntu/+source/acct/tree/dev_hash.c?h=applied/ubuntu/jammy-
devel#n148
--
You received this bu
Validated zfs-linux from plucky-proposed, according to the test case
from the description. I've left the snapshot mount/unmount loop running
for several hours, and no hangs or panics were reported:
root@kadabra:~# zfs version
zfs-2.3.1-1ubuntu2
zfs-kmod-2.3.1-1ubuntu2
root@kadabra:~# apt policy zf
Validated zfs-linux from oracular-proposed, according to the test case
from the description. I've left the snapshot mount/unmount loop running
for several hours, and no hangs or panics were reported:
root@porygon:~# zfs version
zfs-2.2.6-1ubuntu1.2
zfs-kmod-2.2.6-1ubuntu1.2
root@porygon:~# apt pol
Thanks for the changes, @hopem! The revised section on regressions looks
great, and the DEP-3 headers seem to be in place, now.
I've sponsored this for Oracular/Noble/Jammy, thanks!
** Changed in: nova (Ubuntu Oracular)
Status: New => In Progress
** Changed in: nova (Ubuntu Noble)
@zhhuabj thanks for the patches! I've sponsored this with the other nova
uploads for bug 2091033.
I've also added a snippet to the Regression section of the SRU template;
given upstream patches do add test cases for these changes, autopkgtests
should catch most regressions.
Please consider that t
Thanks, Luciano! I've grabbed the relevant patch, and sponsored the
follow-up fix for the version that's currently in noble-proposed.
For the SRU team: based on prior discussions in this bug (comments #15
to #19), we're requesting the "pushing ahead" scenario of [0]. Andreas
has hinted that this w
Thanks, all! Sponsored for Jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1984736
Title:
[SRU]"TypeError: catching classes that do not inherit from
BaseException is not allowed" is raised if
** Changed in: cloud-archive
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972028
Title:
[SRU] _get_pci_passthrough_devices prone to race condition
To manage not
** Description changed:
[Impact]
During repeated NS map/unmap operations in ONTAP (which triggers NS attr
changed AENs) where new NSs get mapped reusing the old NSID, one occasionally
sees the Ubuntu 24.04 NVMe/TCP host ending up with device inconsistencies where
the respective NVMe block d
Thanks for the follow-up, Luciano!
Just to make sure: only the changes in `snapshot-upgrade-fix.patch` are
required, correct? I ran a debdiff between the package from your PPA and
the one currently in noble-proposed, and I've noticed that your PPA also
includes `patch-out-exporter.patch` [0].
I'm
e should pick up those patches for the Ubuntu kernels
as well.
[Test Case]
[Where Problems Could Occur]
** Affects: linux (Ubuntu)
Importance: Medium
Status: Fix Released
** Affects: linux (Ubuntu Noble)
Importance: Medium
Assignee: Heitor Alves de Siqueira (halves)
Hi hopem,
thanks for the debdiffs! The proposed patches seem to be missing
mandatory DEP-3 headers (notably, Origin: and Bug-Ubuntu:), could you
please add those?
Also, could you please give a more detailed account of potential
regressions in the SRU template "[Regression Potential]"? It's usuall
** Changed in: nova (Ubuntu)
Status: New => Fix Released
** Changed in: nova (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: nova (Ubuntu Jammy)
Status: New => In Progress
** Changed in: nova (Ubuntu Jammy)
Assignee: (unassigned) => Edward Hope-Morley (hopem)
This has been sponsored with bug 2074504
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049507
Title:
[SRU] retry on connection error to neutron
To manage notifications about this bug go to:
https:
Thanks for the patches, Rodrigo! I made some minor changes to
debian/changelog, so the bug tracking uses the proper formatting.
Looks good otherwise, sponsored for Jammy/Noble.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
** Changed in: manila (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: manila (Ubuntu Noble)
Assignee: (unassigned) => Rodrigo Barbieri (rodrigo-barbieri2010)
** Changed in: manila (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: manila (Ubuntu Jammy)
As
** Description changed:
Retry https://paste.opendev.org/show/bCtEYsFr0oTfhY9b2r34/
so that a connection error to neutron (maybe due to kubernetes
maintenance) does not immediately lead to share create failure. May be
retry for 5 times with keystone connection failure to avoid duplicate
@hopem yes, I've sponsored this on 2025-05-15. It's currently in the
upload queue [0] with version 3:18.3.5-0ubuntu2.4 (debdiff here [1]).
Although it was well before Focal's end-of-standard-support, the package
has not been released into focal-proposed until now. It's unlikely that
it's going to
Thanks for the changes, Rodrigo! The v2 does align better with the
"minimum required changes" policy, and the rest of the debdiff looks
good as well.
Sponsored for Jammy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
** Changed in: Ubuntu Noble
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2003027
Title:
fq_codel qdisc compiled but not enabled on 22.10
To manage notifica
Thank you, Pon! Some changes I made to your latest debdiff:
- minor changelog adjustments (ubuntu0.1 vs ubuntu1, formatting)
- `Origin: backport` in bug2110614.patch
- added `Backport-Notes:` to bug2110614.patch, explaining the dropped hunks
from upstream
- ran `update-maintainer` as this is the
** Changed in: ksh93u+m (Ubuntu Jammy)
Status: Incomplete => 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/2110614
Title:
[SRU] Honour attributes for local assignments in subshell
** Tags removed: verification-needed-jammy verification-needed-noble
** Tags added: verification-done-jammy verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2101134
Title:
[sru]
Thank you for the bug report, pho! It was well documented, and made it
easier for us to track it down internally. =]
We typically prefer to group more fixes into a single upload (especially
for ZFS, due to the longer running kernel release cycles), but this
seems to be of high enough severity to j
** Description changed:
[Impact]
ZFS mount/unmount operations can leave the storage pools stuck in 'D' state,
preventing access to any datasets.
[Test Plan]
This is not easily reproducible, but seems to happen more frequently when
repeatedly mounting and unmounting ZFS snapshots. Be
** Description changed:
- Every now and then, the `umount` command gets stuck in the `D` state
- when unmounting ZFS snapshots:
+ [Impact]
+ ZFS mount/unmount operations can leave the storage pools stuck in 'D' state,
+ preventing access to any datasets.
+
+ [Test Plan]
+ This is not easily repro
ased
** Also affects: zfs-linux (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: zfs-linux (Ubuntu Plucky)
Importance: Undecided
Status: New
** Also affects: zfs-linux (Ubuntu Questing)
Importance: High
Assignee: Heitor Alves de Siqueira (halves)
Thanks for the patches, @seyeongkim! Your debdiff looks great, and this
seems to be a straightforward fix.
There's a pending openssh package currently going through noble-proposed
(which I see you've based your patches on top of it already, great!).
Once that clears, we can proceed with sponsorshi
Thanks for the patches, @pponnuvel! A few comments below, before this is
ready for upload.
In the debian/changelog entry, please explicitly call out the files
you've modified under the `debian/` folder. For this change, this should
be the new patch file you've added under
`debian/patches/bug211061
Thanks for the patches, Rodrigo!
We've had a quick OOB discussion about the patch context, and the
debdiffs will be slightly adjusted to remove some upstream changes that
are not required for the Ubuntu packages. Once those are addressed, feel
free to let a sponsor know!
** Changed in: python-ope
Hi Bryan!
Thanks for the patches! We should probably get debdiffs for the
"regular" Ubuntu series into -proposed first, then look into the UCA
series. A note on your debdiffs, format-related comments only:
- some of your debian/changelog entries seem to be merged with a previous entry
(Zed, Cara
** Changed in: nova (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: nova (Ubuntu Noble)
Status: New => In Progress
** Changed in: nova (Ubuntu Noble)
Assignee: (unassigned) => Hua Zhang (zhhuabj)
** Changed in: nova (Ubuntu Oracular)
Importance: Undecided => Mediu
** Changed in: nagios-nrpe (Ubuntu Focal)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2023263
Title:
nrpe crash in free() upon connection tear down
To manage noti
** Also affects: ksh93u+m (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ksh93u+m (Ubuntu Noble)
Status: New => Fix Released
** Changed in: ksh93u+m (Ubuntu)
Status: New => Fix Released
** Changed in: ksh93u+m (Ubuntu Jammy)
Status: New => Triaged
** Ch
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => High
** Changed in: zfs-linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are
Already present in the 6.14 kernels, marking Plucky onward as Fix
Released.
** Changed in: linux (Ubuntu Plucky)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubun
Thanks for the patches, Rodrigo! Your debdiff has some cruft in it, but
the actual patches look good. Given Focal is almost EOL, it'd be great
if we could get this tested as soon as it hits proposed.
Sponsored for Focal.
** Changed in: horizon (Ubuntu Focal)
Status: New => In Progress
--
** Description changed:
* SRU TEMPLATE AT THE BOTTOM
OpenStack/Horizon: Yoga
After creating an instance
# openstack server show test2 | egrep 'flavor| id '
| flavor | gen.medium (gen.medium)
| id
** Changed in: horizon (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: cloud-archive/ussuri
Importance: Undecided => High
** Changed in: horizon (Ubuntu Focal)
Importance: Medium => High
** Changed in: cloud-archive/ussuri
Assignee: (unassigned) => Rodrigo Barbieri (r
Thanks for the clarification, Luciano! I've adjusted the versions, and
uploaded builds to a test PPA at [0]. I've also ran autopkgtests against
those builds, and things look good on that front. Let's tackle the
Oracular/Noble versions now, and we can look into UCA once those hit
-proposed.
Sponsor
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
** Changed in: linux (Ubuntu Oracular)
Status: Invalid => Fix Released
** Changed in: linux (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Oracular)
Importance: Undecided => Medium
**
As per Luciano's comment in bug 2097605, Oracular is not affected by
this. Updating the bug status accordingly.
** Changed in: ceph (Ubuntu Oracular)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Changed in: ceph (Ubuntu Oracular)
Status: Incomplete => 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/2097605
Title:
[SRU] Squid: Ceph new point release 19.2.1
To manage noti
** Changed in: ceph (Ubuntu Oracular)
Assignee: Peter Sabaini (peter-sabaini) => Luciano Lo Giudice (lmlogiudice)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089565
Title:
MON and MDS crash
Hi Luciano,
thanks for the builds! I noticed that the oracular build does not
include snapshot-upgrade-fix.patch, which seems to be the fix for bug
2089565. It's present in the point release candidate for Noble, do we
need it for Oracular as well?
** Changed in: ceph (Ubuntu Oracular)
Assign
Marking as incomplete as per previous comment, please feel free to move
it back once we have a conclusion on the fixes and/or upstream
discussion!
** Changed in: python-etcd3gw (Ubuntu Oracular)
Status: In Progress => Incomplete
** Changed in: python-etcd3gw (Ubuntu Noble)
Status: I
** Changed in: glib2.0 (Ubuntu Plucky)
Importance: Undecided => Medium
** Changed in: glib2.0 (Ubuntu Oracular)
Importance: Undecided => Medium
** Changed in: glib2.0 (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: glib2.0 (Ubuntu Jammy)
Importance: Undecided => Medium
Hi Nick!
Thank you for the bug and the debdiffs! Like liushuyu mentioned, we'll need to
rework this one so it's compliant to the SRU policy. From a brief review, these
are the items I could spot:
- please include the SRU template in the bug description [0]
- there's a '+soss1' in the version of yo
** Changed in: llvm-toolchain-16 (Ubuntu)
Status: New => Fix Released
** Changed in: llvm-toolchain-15 (Ubuntu)
Status: New => Fix Released
** Changed in: llvm-toolchain-14 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member o
** Changed in: xrdp (Ubuntu Jammy)
Status: Confirmed => 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/1960174
Title:
Getting error during login attempt: "error loading libvnc.so s
Thanks for the patches, Gerald! I've tested this on my personal PPA, and
sponsored for Oracular and Noble. I've also amended the SRU template in
the "Where problems could occur" section.
Note that this is blocked for Jammy/Focal due to packages for bug
2056187 being in -proposed. Once that clears
** Description changed:
[Impact]
According to netplan doc
https://netplan.readthedocs.io/en/latest/netplan-yaml
gateway4/gateway6 are deprecated and the first version deprecates these
fields is 0.103,
it should use "routes:" instead.
In scripts/functions:_render_netplan, it s
Thank you, Rodrigo! This looks great now, I'll pull it in for the next
nova release.
We're currently blocked by the version in proposed due to bug 1972028,
once that clears we can proceed with a new release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078467
Title:
[SRU] App armor crashes on aa-enforce due to "Profile not found
Hi Peter, Pon,
I've reviewed the packages from Peter's PPA [0] for Noble and Oracular. To
adjust those for the archives, I rebuilt them as 19.2.1-0ubuntu0.24.04.1 and
19.2.1-0ubuntu0.24.10.1 respectively (so the upgrade path is valid between all
Ubuntu archive packages).
The noble packages look O
** Changed in: ceph (Ubuntu Oracular)
Status: Triaged => In Progress
** Changed in: ceph (Ubuntu Noble)
Status: Triaged => In Progress
** Changed in: ceph (Ubuntu Noble)
Assignee: (unassigned) => Peter Sabaini (peter-sabaini)
** Changed in: ceph (Ubuntu Oracular)
Assignee
** Changed in: ceph (Ubuntu Oracular)
Status: Triaged => In Progress
** Changed in: ceph (Ubuntu Noble)
Status: Triaged => In Progress
** Changed in: ceph (Ubuntu Noble)
Assignee: (unassigned) => Peter Sabaini (peter-sabaini)
** Changed in: ceph (Ubuntu Oracular)
Assignee
*** This bug is a duplicate of bug 2097605 ***
https://bugs.launchpad.net/bugs/2097605
I'm marking this one as a duplicate of bug 2097605, as it's included in
the 19.2.1 release according to upstream [0][1]. We should get 19.2.1
released instead, given Ceph already has an SRU exception as part
Hi Andreas, Mike,
I've been testing both options last week, and looking at the results I'll now
agree with mike :)
The alternative fix from comment 19 seems to work correctly for the leftover
mount points, and does not seem to have issues with the grub entries (it's
available for Jammy under [0
Well, Oracular does fix the reported bug (i.e. it cleans up spurious
leftover mounts) but it can also cause os-prober to create invalid GRUB
entries like Mike mentioned.
I'll follow it up with a fix regardless, so I'm not sure if the best way
for the current version is to keep in in oracular-propo
Validated on an Oracular VM, according to test case from the
description. I'm unable to reproduce the issue with the new package
version, and spotted no other regressions:
ubuntu@ubuntu2410:~$ sudo update-grub; sudo update-grub; mount | tail
Sourcing file `/etc/default/grub'
Sourcing file `/etc/de
** Changed in: sosreport (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: sosreport (Ubuntu Noble)
Status: Confirmed => In Progress
** Changed in: sosreport (Ubuntu Jammy)
Status: Confirmed => In Progress
** Changed in: sosreport (Ubuntu Oracular)
Status
I've tested and validated this on the scenarios mentioned in the bug
description. The summary is below:
- ZFS only setup ✅
- LUKS only ✅
- ZFS on LUKS ✅
The first two scenarios are easily accessible from the default Ubuntu
Desktop Installer for Focal. For ZFS on LUKS, I followed the upstream
ZFS
** Changed in: os-prober (Ubuntu Noble)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1987679
Title:
os-prober leaves filesystems (lvm-thin, lvm snap) mounte
Hi Rodrigo,
thanks for the Jammy patch! I'd like to get a bit more clarification on
a few things:
- on your SRU template, please rework the regression section. It's
usually assumed that proposed patches go through testing and that we do
whatever possible to minimize regressions, but this should a
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078467
Title:
[SRU] App armor crashes on aa-enforce due to "Profile not found"
T
*** This bug is a duplicate of bug 2087852 ***
https://bugs.launchpad.net/bugs/2087852
** This bug has been marked a duplicate of bug 2087852
Repository profiles only act on .list files and do not affect .source files
--
You received this bug notification because you are a member of Ubunt
** Changed in: landscape-client
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103463
Title:
[SRU] Repository profiles only act on .list files and do not affect
The fix commit [0] was introduced in systemd v252, so it's already fixed
starting with Noble.
[0]
https://github.com/systemd/systemd/commit/c75efa3f7e34eb593e2a6df1313ba8fdcbe729c1
** Changed in: systemd (Ubuntu)
Status: Invalid => Fix Released
** Changed in: systemd (Ubuntu Oracular)
Validated on Noble aarch64, using the scripts and test case from
description. Kernel logs are clear, and I was unable to reproduce the
page allocation failure.
ubuntu@gunyolk:~$ sudo dmesg -c; ./repro.bash; sudo dmesg; uname -rv
+ ulimit -S -c unlimited
+ cc ./alloc_and_crash.c -o ./alloc_and_cras
1 - 100 of 482 matches
Mail list logo