** Changed in: linux (Ubuntu Focal)
Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1981487
Title:
kernel BUG/Oops errors from modpr
** Changed in: requests (Ubuntu Noble)
Assignee: Mauricio Faria de Oliveira (mfo) => Ioanna Alifieraki (joalif)
** Changed in: requests (Ubuntu Jammy)
Assignee: Mauricio Faria de Oliveira (mfo) => Ioanna Alifieraki (joalif)
--
You received this bug notification because you
efit from a
+significant performance improvement.
+(Summary in comment 4, some context in comment 5.)
** Changed in: python-urllib3 (Ubuntu Jammy)
Assignee: Mauricio Faria de Oliveira (mfo) => Ioanna Alifieraki (joalif)
** Changed in: requests (Ubuntu Jammy)
Assignee: Mauricio Faria de
** Description changed:
- WIP.
+ [Impact]
+
+ * The HTTPS certificate verification in Python Requests
+may be *incorrectly* ignored if an existing connection
+to the same host previously did *not* use verification.
+
+ [Test Plan]
+
+ * Create session to perform _first_ a request
Note: test packages used above are available in ppa:mfo/lp2091732-lp2091733,
but are still missing patches to address reports of functional regressions
in the upstream project, which plans to revert this change (6667/6767 [2,3]),
although this has not yet been applied for some months now.
Most sho
Note: test packages used above are available in ppa:mfo/lp2091732-lp2091733,
but are still missing patches to address reports of functional regressions
in the upstream project, related to the change for bug 2091733 (not this one),
(6667/6767 [2,3]), although this has not yet been applied for some m
$ cat ./test-https-verify.py
#!/usr/bin/python3
import requests
def test_https_verify(session, verify):
"""
Try an HTTPS request to a server with a bad SSL certificate.
If certificate verification is enabled, this _should_ fail.
The bug is, an existing connection (in the connectio
Noble:
---
Before (one BAD):
$ dpkg -s python3-requests | grep -e Package: -e Version:
Package: python3-requests
Version: 2.31.0+dfsg-1ubuntu1
$ ./test-https-verify.py
Test 1A - verification enabled
Should Fail (GOOD)
Test 1B - verification disabled
/usr/lib/python3/dist-packages/urllib3/connec
Noble:
---
Before:
$ dpkg -s python3-requests | grep -e Package: -e Version:
Package: python3-requests
Version: 2.31.0+dfsg-1ubuntu1
$ ./test-https-concurrent.py
Run: 0, Time: 3774 ms
Run: 1, Time: 3604 ms
Run: 2, Time: 3618 ms
Run: 3, Time: 3692 ms
Run: 4, Time: 3649 ms
Run: 5, Time: 3501 ms
Ru
Jammy:
---
Before (one BAD):
$ dpkg -s python3-requests python3-urllib3 | grep -e Package: -e Version:
Package: python3-requests
Version: 2.25.1+dfsg-2ubuntu0.1
Package: python3-urllib3
Version: 1.26.5-1~exp1ubuntu0.2
$ ./test-https-verify.py
Test 1A - verification enabled
Should Fail (GOOD)
Te
Jammy:
---
Before:
$ dpkg -s python3-requests python3-urllib3 | grep -e Package: -e Version:
Package: python3-requests
Version: 2.25.1+dfsg-2ubuntu0.1
Package: python3-urllib3
Version: 1.26.5-1~exp1ubuntu0.2
$ ./test-https-concurrent.py
Run: 0, Time: 3735 ms
Run: 1, Time: 4072 ms
Run: 2, Time: 4
$ cat ./test-https-concurrent.py
#!/usr/bin/python3
import requests
import concurrent.futures
import time
from statistics import mean, median
def run_https_get():
return requests.get('https://example.com').content
def run_https_get_concurrent():
with concurrent.futures.ThreadPoolExecutor(
The verification of the Stable Release Update for packagekit has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounte
Verified with debdiff that all debs, in all archs, have no other
changes.
Every deb has changes to the Version: and versioned Depends: in other debs of
src:packagekit.
But _only_ packagekit:armhf has a versioned Depends: change in something else,
which is the expected 'libapt-pkg6.0t64' (from 2.
Thanks for the detailed bug reports/SRU templates and backport notes,
Nick.
I can confirm everything in the incremental upload (249.11-0ubuntu3.14
on top of 3.13 in jammy-proposed) looks in order, and the changes are
present in Noble.
A minor nit: in the DEP-3 headers (thanks!), since you had to
Hello frantisek, or anyone else affected,
Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.14 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
htt
Hello Skia, or anyone else affected,
Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.14 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Hello Nick, or anyone else affected,
Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.14 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Hello Danilo, or anyone else affected,
Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.14 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
Hello Chengen, or anyone else affected,
Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.14 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
Hi Ram Sun,
Thanks for the bug report and detailed versions.
If I understand correctly, you report slow mounts with a version in Jammy
(1:2.6.1-1ubuntu1.2),
and that the issue does _not_ happen with the versions in Focal
(1:1.3.4-2.5ubuntu3) and Noble (1:2.6.4-3ubuntu5), which are different Ubu
** Summary changed:
- Performance improvement on SSL connections
+ Performance improvement on concurrent SSL connections
** Summary changed:
- Performance improvement on concurrent SSL connections
+ Performance improvement for concurrent SSL connections
--
You received this bug notification be
Faria de Oliveira (mfo)
Status: In Progress
** Affects: requests (Ubuntu Jammy)
Importance: Medium
Assignee: Mauricio Faria de Oliveira (mfo)
Status: In Progress
** Affects: python-urllib3 (Ubuntu Noble)
Importance: Undecided
Status: Invalid
** Affects
Public bug reported:
WIP.
** Affects: requests (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: requests (Ubuntu Jammy)
Importance: Medium
Assignee: Mauricio Faria de Oliveira (mfo)
Status: In Progress
** Affects: requests (Ubuntu Noble
The update_excuses page for jammy is currently outdated (Dec. 4th)
and I'm asking for it to be looked at by the responsible team.
Considering what is already there and in the pending-sru page,
plus other checks, only autopkgtests still need to be verified.
I did that manually with the autopkgtest
This request has been rejected.
Some snippets fo the rationale:
- While it is true that packages in universe are supported in Pro,
Python modules are only built for the supported Python versions.
- Python extensions are packaged for use with the default Python interpreter
version.
Other
Hey Alan. Thanks, that looks good!
The Test Plan has been successfully executed, and other checks for release look
in order.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077382
Title:
[SRU] suppo
The verification of the Stable Release Update for python-libmaas has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you enco
** Description changed:
[Impact]
Some gcc versions in Jammy and Focal are still
vulnerable to the arm64-specific CVE-2023-4039
(-fstack-protector guard failures with dynamic
stack allocations).
This impacts detecting, e.g., buffer overflows,
resulting in less secure Ubuntu arm6
That build PPA had issues with disk space on amd64, which seem to be more
persistent than what retries are helping with. I'm reaching out to the LP
team about it.
https://launchpad.net/~mfo/+archive/ubuntu/lp2054343-sru
However, the amd64 builds worked fine in a previous build PPA, so doesn't
see
The verification of the Stable Release Update for sosreport has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
Hi Alan,
If I'm reading it right and not missing anything, the screenshots of the
MAAS UI are an alternative (not the CLI commands in the Test Plan) that
can confirm the 'Hardware sync' part -- as it shows 'Periodic hardware
sync enabled'.
Does anything in there tell whether or not the deployment
The verification of the Stable Release Update for sosreport has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
Hi Alan,
Thanks for performing the verification steps!
Even though the script exercises the new parameters, it does not verify
whether they actually worked (i.e., not just pure code changes).
I understood this is why the Test Plan includes the steps to 'manually
validate an Ephemeral deployment'
The verification of the Stable Release Update for open-iscsi has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounte
The verification of the Stable Release Update for sssd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a reg
Thanks, Erich for your work on this SRU. It looks good for release!
s390x does FTBFS (not mentioned in this bug), but this is not a
regression, it happens in the release pocket too [1], thus not a
blocker.
[1]
https://launchpad.net/ubuntu/+source/audacity/3.6.1+dfsg-1/+build/28678103
--
You rec
The verification of the Stable Release Update for audacity has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
Autopkgtests are clear now.
Arif, the new upload triggered the verification-needed again.
Considering you already did a thorough verification previously
with the complete test plan, and the last upload is just a fix
for autopkgtests without behavior changes, it seems reasonable
that just the basi
Retried the autopkgtests above. Some seem to be infrastructure issues
that persist, so I'm rerunning with migration-reference/0 as the
trigger, so they don't become blockers, as the issues aren't related to
these changes.
--
You received this bug notification because you are a member of Ubuntu
Bu
Regarding comment #19:
- AFAIK, patch 7 ("Fix syscall error on non-x86 platform") only restricts
non-x86 platforms of code introduced in patch 3 ("Invoke the syscall to
allow the use of amx tiles"), thus such code did not exist in previous
versions of the package, so was not present in non-x
Question about patch 6 ("... gcc version check error")
- This changes the enablement of `-march=sapphirerapids` to gcc-11 from
gcc-10, which is available in Jammy (although rebuilding an official
package makes it non-official/not supported), but is not described in
the upstream PR.
Do y
Hi Hector,
Thanks for the work on this fix for Sapphire Rapids in Jammy!
I've looked at this bug and patchset -- which looks good IMHO -- but I thought
of some points.
I'll split those in multiple comments for clarity.
Happy to accept these changes with these addressed; please feel to free to p
Test requirements (this is required and block this SRU, in my opinion)
- Even though the patches are targeted only against Sapphire Rapids,
it is important that the Test Plan covers other CPU models too.
This is to ensure not only the fix for Sapphire Rapids is correct,
but also that there
Style suggestions (not required at all, but helpful; not a blocker):
- For sets of patches, if per-patch changelog entries are not warranted,
filenames with the LP bug are a nice way to generically still mention
the files in the changelog; e.g., 'd/p/lp--*.patch:
something (LP: #bug)'.
-
Hello Philip, or anyone else affected,
Accepted policykit-1 into noble-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/policykit-1/124-2ubuntu1.24.04.2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Philip, or anyone else affected,
Accepted policykit-1 into oracular-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/policykit-1/124-2ubuntu1.24.10.2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package
All approved and merged.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2038648
Title:
package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade:
installed sosreport package post-installatio
** Attachment added: "test-glibc-malloc.c"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2089789/+attachment/5841534/+files/test-glibc-malloc.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
** Description changed:
[Impact]
* Jammy has a malloc() performance degradation
if CPU affinity masks are used (not default).
* The maximum number of arenas for malloc() is
calculated based on the number of processors.
However, glibc 2.34 changed that to be based
Coordinated this SRU with Simon Chopin in Foundations,
who handles most glibc uploads; this will be discussed
and planned for the next round of bug-fixes/glibc SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Debdiff used for the PPA builds (successful in all architectures).
** Patch added: "lp2089789-glibc-jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2089789/+attachment/5840918/+files/lp2089789-glibc-jammy.debdiff
--
You received this bug notification because you are a mem
Build-testing in all supported architectures in a PPA with only the -security
pocket enabled.
https://launchpad.net/~mfo/+archive/ubuntu/lp2089789
** Description changed:
[Impact]
- * Jammy has a malloc() performance degradation
-if CPU affinity masks are used (not default).
+ * Jammy
** Description changed:
- https://sourceware.org/bugzilla/show_bug.cgi?id=30945
+ [Impact]
+
+ * Jammy has a malloc() performance degradation
+if CPU affinity masks are used (not default).
+
+ * The maximum number of arenas for malloc() is
+calculated based on the number of processors.
Now with the patch [1] applied, it is back to normal.
$ dpkg -s libc6 | grep Version:
Version: 2.35-0ubuntu3.8+gd47c5e4db792
Without per-CPU affinity (average: 63ms) -- no regression
$ ./test-glibc-malloc 56 false false
nr_cpu: 56 pin: no fix: no
thread average (ms): 69.9
Some snippets (more line breaks for clarity) from
https://sourceware.org/bugzilla/show_bug.cgi?id=30945
"""
<...> The deserialization library we used works 10x slower than
expected.
Investigations show that this is due to the arena_get2 function uses
__get_nprocs_
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089789
Title:
malloc performance degradation with CPU affinity masks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+s
Reproducer with a Jammy LXD container.
System with 56 processors ("threads").
LXD and gcc setup:
$ lxc launch ubuntu:jammy glibc-jammy
$ lxc exec glibc-jammy -- su - ubuntu
$ wget -O test-glibc-malloc.c
https://sourceware.org/bugzilla/attachment.cgi?id=15156
$ su
Checking for required dependencies of the last commit above:
---
Commits in-between the first offender and final fix, in the development
branch:
$ git log --oneline origin/master --
sysdeps/unix/sysv/linux/getsysstats.c | grep -v 'Update copyright dates'
472894d2cfee malloc: Use
Related git commits, starting with the first related change, and finishing with
the fix required.
The intermediary commits provide some context used later to understand the
required dependencies.
---
The initial commit changed __get_nprocs() to use sched_getaffinity()
instead of sysfs and procfs
** Description changed:
- WIP.
+ https://sourceware.org/bugzilla/show_bug.cgi?id=30945
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089789
Title:
malloc performance degradation with CPU affinity
Public bug reported:
WIP.
** Affects: glibc (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: glibc (Ubuntu Jammy)
Importance: Medium
Assignee: Mauricio Faria de Oliveira (mfo)
Status: Confirmed
** Also affects: glibc (Ubuntu Jammy)
Importance
badtests:
bionic
https://code.launchpad.net/~mfo/britney/+git/britney/+merge/477367
focal
https://code.launchpad.net/~mfo/britney/+git/britney/+merge/477366
jammy
https://code.launchpad.net/~mfo/britney/+git/britney/+merge/477364
noble
https://code.launchpad.net/~mfo/britney/+git/britney/+merge
Hi Arif,
Thanks for clarifying, and looking into this!
I can see that pattern of fail/pass in autopkgtests for ppc64el (only).
Since this is test infrastructure related, and other architectures are
still run thus can provide some level of confidence about SRU changes,
it should be OK to add a te
Hi Arif,
The autopkgtests issues for the MAC address obfuscation are fixed,
thanks!
However, there's one still pending for IP address obfuscation in ppc64el only
(which is also present in the previous upload, checking the autopkgtest logs).
Could you please address that one too? The other archs
I'll build the package with the incremental fix for autopkgtests in a PPA, and
trigger autopkgtests against it to validate it is all good -- and if so, upload
to Bionic.
I had minor changes to the changelog entry and added the `Bug-Ubuntu:` DEP-3
header to the .patch file.
Thanks again!
--
Yo
Hi Arif,
Thanks for addressing the request for completing
the test plan (comment #44)! All good with this:
> 3) Compare terminal output, apt history, `dpkg -l`
> between each cases, and check for no differences
> in package install order, or unexpected things.
> (see comments 19-31).
The diffs f
Uploaded to Jammy and Focal.
** Changed in: sosreport (Ubuntu Focal)
Status: New => In Progress
** Changed in: sosreport (Ubuntu Jammy)
Status: New => In Progress
** Changed in: sosreport (Ubuntu Focal)
Assignee: (unassigned) => Arif Ali (arif-ali)
** Changed in: sosreport (U
Test package from PPA works correctly (jammy).
$ wget
https://launchpad.net/~mfo/+archive/ubuntu/build-proposed/+build/29305804/+files/sosreport_4.7.2-0ubuntu1~22.04.2_amd64.deb
$ sudo apt install ./sosreport_4.7.2-0ubuntu1~22.04.2_amd64.deb
$ dpkg -s sosreport | grep Version:
Version: 4.7.2-0ub
Test package from PPA works correctly (focal).
$ wget
https://launchpad.net/~mfo/+archive/ubuntu/build-proposed/+build/29305816/+files/sosreport_4.7.2-0ubuntu1~20.04.2_amd64.deb
$ sudo apt install ./sosreport_4.7.2-0ubuntu1~20.04.2_amd64.deb
$ dpkg -s sosreport | grep Version:
Version: 4.7.2-0ub
For reference, sosreport in Noble (note the informational messages):
$ lsb_release -cs
No LSB modules are available.
noble
$ uname -r
6.8.0-49-generic
$ lsmod | grep msr
$
$ sudo cpupower info
System does not support Intel's performance bias setting
analyzing CPU 0:
$ lsmod | grep msr
msr
For reference, sosreport in jammy (note _no_ informational messages)
$ lsb_release -cs
jammy
$ uname -r
5.15.0-126-generic
$ lsmod | grep msr
$
$ sudo cpupower info
System does not support Intel's performance bias setting
analyzing CPU 0:
$ lsmod | grep msr
msr16384 0
$ s
For reference, sosreport in jammy (note _no_ informational messages)
$ lsb_release -cs
focal
$ uname -r
5.4.0-200-generic
$ lsmod | grep msr
$
$ sudo cpupower info
System does not support Intel's performance bias setting
analyzing CPU 0:
$ lsmod | grep msr
msr16384 0
$ s
** Also affects: sosreport (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: sosreport (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: sosreport (Ubuntu Plucky)
Importance: Undecided
Status: New
** Also affects: sosreport (Ubuntu Fo
Public bug reported:
.
** Affects: sosreport (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089713
Title:
The processor plugin loads the ms
Hi Joshua,
Thanks for your work on this!
Regarding the debdiff for SRU to Jammy in comment #27.
1) Please fix the version for stable releases (increment of ubuntu0.1,
usually), not development series (increment of ubuntu1, usually).
See the versioning reference [1].
2) Please add DEP-3 headers
The verification of the Stable Release Update for dmidecode has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
It passed.
crmsh [noble/i386]
Version TriggersEnv DateDurationRequester
Result UUID
4.6.0-1ubuntu2 dmidecode/3.5-3ubuntu0.12024-11-25 22:04:36 UTC
0h 13m 34s mfo pass855eb873-69a4-412d-89de-dd49edac061f
log ar
Noble should be good for release, except for an i386 autopkgtest that
apparently never finished [1]:
autopkgtest for crmsh/4.6.0-1ubuntu2: amd64: Pass, arm64: Pass, armhf:
Pass, i386: Test in progress, ppc64el: Pass, s390x: Pass
I triggered a rerun for it; hopefully it may finish during my SRU
va
Hello Joao, or anyone else affected,
Accepted dmidecode into jammy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/dmidecode/3.3-3ubuntu0.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Script:
---
VERSION=''
BASEURL='https://launchpad.net/ubuntu/+archive/primary/+files/'
for ARCH in amd64 arm64 armhf ppc64el riscv64 s390x; do
echo $ARCH
mkdir $ARCH
pushd $ARCH >/dev/null
mkdir ddebs
for PKG in python3-pil python3-pil.imagetk; do
DBGPKG="${PKG}-dbgsym_${VERSION}
The change is present in Oracular (10.4.0-1ubuntu1) via bug 2077744.
** Changed in: pillow (Ubuntu Oracular)
Status: Invalid => 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/208445
Hi Mate,
Thanks for the work on this, and verifying with Julian's script.
In the future, please include further details (e.g., in this case there
are two scripts, without a mention of which was used, although it seems
likely dwprod.py) and version tested (surprisingly, there are cases
where peopl
and 'Wants='
('Wants=' is not generated by pkgos-gen-systemd-unit currently).
- d/cinder-volume.install: ship the systemd service drop-in file.
-- Mauricio Faria de Oliveira Fri, 06 Sep 2024
13:47:33 -0300
** Changed in: ubuntu-pro/18.04
Status: Fix Committed => Fix Re
** Changed in: ubuntu-pro/18.04
Status: In Progress => Fix Committed
** Tags added: verification-done-pro-18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1987663
Title:
cinder-volume: "F
Verification done on bionic's ESM Infra Updates -staging ("-proposed").
The detailed verification steps as per comment #3
are attached. This is the summary with key steps.
With the packages from -staging, when (re)starting {cinder-volume,tgt}.service,
the cinder-volume service is started _after_
Sponsored to Oracular, Noble, and Jammy.
Thanks for all the work on this, Alan!
** Changed in: python-libmaas (Ubuntu Plucky)
Importance: High => Undecided
** Changed in: python-libmaas (Ubuntu Plucky)
Assignee: Alan Baghumian (alanbach) => (unassigned)
** Changed in: python-libmaas (Ubu
** Description changed:
[ Impact ]
* This SRU is not addressing an existing problem but adds support for
two additional optional parameters being ephemeral_deploy and
enable_hw_sync on deploy(). For more details please see (1).
+ * The code changes align with the SRU policy's "Other
Also, it would be nice to measure/validate the performance improvement
with a fake, synthetic, very large /proc/mounts file (e.g., mount -o
bind /tmp/fake-mounts /proc/mounts), in the order of the problematic
LDAP file mentioned in the [Impact] section, since this is what the SRU
is about: i.e., ol
Hi Chengen,
I'm resuming the reviews for these SRUs.
At the moment, the Test Plan section is a bit vague:
Can you please clarify what is the expected output of running cryptroot?
And IMHO it could be improved with a specific test for regressions (the key
point in SRUs is to maintain stability/a
The proposed change is already applied in Oracular and Plucky.
$ rmadison -a source cryptsetup
...
cryptsetup | 2:2.7.2-2ubuntu1 | oracular | source
cryptsetup | 2:2.7.2-2ubuntu1 | plucky | source
$ pull-lp-source cryptsetup
Found cryptsetup 2:2.7.2-2ubuntu1 in plucky
$ grep
** Also affects: gce-compute-image-packages (Ubuntu Plucky)
Importance: Undecided
Assignee: Chloé Smith (kajiya)
Status: Fix Released
** Also affects: gce-compute-image-packages (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: gce-compute-image-packages (
Hello Chloé, or anyone else affected,
Accepted google-guest-agent into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/google-
guest-agent/20241011.01-0ubuntu1~20.04.0 in a few hours, and then in the
-proposed repository.
Please help us by testi
** Also affects: google-osconfig-agent (Ubuntu Plucky)
Importance: Undecided
Assignee: Chloé Smith (kajiya)
Status: Fix Released
** Also affects: google-osconfig-agent (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: google-osconfig-agent (Ubuntu Oracular
Hello Chloé, or anyone else affected,
Accepted google-guest-agent into jammy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/google-
guest-agent/20241011.01-0ubuntu1~22.04.0 in a few hours, and then in the
-proposed repository.
Please help us by testi
Hello Chloé, or anyone else affected,
Accepted google-guest-agent into noble-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/google-
guest-agent/20241011.01-0ubuntu1~24.04.0 in a few hours, and then in the
-proposed repository.
Please help us by testi
Hello Chloé, or anyone else affected,
Accepted google-guest-agent into oracular-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/google-guest-
agent/20241011.01-0ubuntu1~24.10.0 in a few hours, and then in the
-proposed repository.
Please help us by te
3) Very important, AFAICT, there are non-trivial changes to:
- Network configuration management
- OS login and SSH
- networkctl/dhclient
In order to mitigate the regression potential of _inaccessible instances_
after a _package upgrade_ (and maybe reboot), can we have a confirmation
of such testin
Hi Chloé,
Thanks for the big work on this! Some notes:
1) The bug was not targeted against the Ubuntu series for SRU (O/N/J/F).
I handled it, no problem, but just wondered if it was an oversight or
permissions -- do you see 'Target to series' link above 'Bug Description' ?
2) The section on ven
** Also affects: google-guest-agent (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: google-guest-agent (Ubuntu Plucky)
Importance: Undecided
Assignee: Chloé Smith (kajiya)
Status: Fix Released
** Also affects: google-guest-agent (Ubuntu Focal)
Importa
1 - 100 of 1659 matches
Mail list logo
