Likewise for Focal. Uploaded!
** Changed in: nova (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: nova (Ubuntu Focal)
Status: New => In Progress
** Changed in: nova (Ubuntu Focal)
Assignee: (unassigned) => Rodrigo Barbieri (rodrigo-barbieri2010)
--
You received
Rebased, reviewed, and build-tested on PPA [1].
Uploaded to Focal.
[1] https://launchpad.net/~mfo/+archive/ubuntu/lp1999814
** Description changed:
+ [ Impact ]
+
+ * Live migration is increasingly being impacted by changes to CPU flags
+(e.g., 'xsaves' disabled on AMD EPYC; PKRU/'xsave'
** Changed in: nova (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: nova (Ubuntu Jammy)
Assignee: (unassigned) => Rodrigo Barbieri (rodrigo-barbieri2010)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
riaged
** Changed in: nova (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: nova (Ubuntu Focal)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: nova (Ubuntu)
Status: Triaged => Fix Released
** Changed in: nova (Ubuntu)
Imp
Hi Rodrigo,
Thanks for the debdiffs and SRU template!
I've had minor changes to the Jammy upload, and build-tested it in a PPA [1].
It looks good; uploading!
(I'm looking into/building Focal.)
[1] https://launchpad.net/~mfo/+archive/ubuntu/lp1999814
** Changed in: nova (Ubuntu Jammy)
Debdiff for Antelope for bugs 1728031, 2054799, and 2055409.
Build-tested on ppa:mfo/horizon-lp1728031-lp2054799-lp2055409-antelope [1] with
antelope-updates enabled.
Now looking for sponsorship to the cloud-archive.
[1] https://launchpad.net/~mfo/+archive/ubuntu/horizon-
** Changed in: cloud-archive/antelope
Importance: Undecided => Medium
** Changed in: cloud-archive/antelope
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054799
** Changed in: cloud-archive/antelope
Importance: Undecided => Medium
** Changed in: cloud-archive/antelope
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055409
The patch cannot be applied to Ubuntu Bionic (18.04), since its libvirt
version is older than the minimum required (mentioned in the patch).
The Ubuntu Cloud Archive for Bionic (eg, from Focal / Ussuri) can be
used/patched though, as it provides a sufficiently newer version of
libvirt.
`QEMU
The patch is present in Ubuntu Mantic and later.
$ git grep skip_cpu_compare_at_startup pkg/ubuntu/oracular-devel --
nova/conf/workarounds.py
pkg/ubuntu/oracular-devel:nova/conf/workarounds.py:
cfg.BoolOpt('skip_cpu_compare_at_startup',
$ git grep skip_cpu_compare_at_startup
Hi Chengen,
Thanks for implementing this!
Could you please confirm/describe the testing
performed with this additional patch/option?
** Changed in: cinder (Ubuntu Jammy)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi Arif,
Thanks for testing!
Could you please also check/confirm the steps 3 and 4 of the Test Plan,
as we did in previous comments for testing, per the point in comment 3?
** Tags removed: verification-done-bionic
** Tags added: verification-needed-bionic
--
You received this bug
** Description changed:
[Impact]
Originally, Nova archives deleted rows in batches consisting of a maximum
number of parent rows (max_rows) plus their child rows, all within a single
database transaction.
This approach limits the maximum value of max_rows that can be specified by
the
Hi Ed and Chengen,
Ed, thanks for your review and feedback.
> I think that to make this patch really same some guardrails should be
put in place.
> it might have been safer to make this an optional feature, defaulting
to disabled
This also aligns with Dan's feedback (internal):
> there are
** Changed in: sosreport (Ubuntu Bionic)
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/2038648
Title:
package sosreport 4.4-1ubuntu0.18.04.1 failed to
Hi Arif,
Thanks for checking and confirming the locale changes are unrelated!
I suspected the locale difference were unrelated, but wanted a closer
look and clear understanding of why, before uploading, to ensure our
changes to Bionic demonstrate the required care to request an upload
in the
Hi Lukas,
Thanks for the assistance in sponsoring!
I had other changes to make in the upload (in the PPA),
so I'll reject this one and continue with that; sorry,
I should have made that clearer in my previous comment.
cheers,
--
You received this bug notification because you are a member of
Hi Arif,
I've reviewed, updated SRU template, and built packages in a PPA [1].
It looks good, but there's an apparently unrelated change: some locale
files are now in the sosreport deb package (pasted below).
Could you please take a look?
Thanks!
Mauricio
[1]
** Description changed:
- [impact]
+ [ Impact ]
+
+ On release upgrade from Xenial to Bionic,
+ there seems to be an unknown corner case
+ (difficult to reproduce) that Python 3.5
+ from Xenial is still in place at the time
+ sosreport from Bionic is installed, which
+ breaks postinst/py3compile
Hi Jacob,
Thanks for testing; that's good news.
Package uploaded to Jammy; now waiting on review by the SRU team.
cheers,
Mauricio
** Changed in: python-rtslib-fb (Ubuntu Jammy)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Hello L, or anyone else affected,
Accepted ubuntu-advantage-tools into bionic-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/32.3.1~18.04
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello L, or anyone else affected,
Accepted ubuntu-advantage-tools into focal-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/32.3.1~20.04
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello L, or anyone else affected,
Accepted ubuntu-advantage-tools into xenial-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/32.3.1~16.04
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello L, or anyone else affected,
Accepted ubuntu-advantage-tools into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/32.3.1~22.04
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello L, or anyone else affected,
Accepted ubuntu-advantage-tools into mantic-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/32.3.1~23.10
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello L, or anyone else affected,
Accepted ubuntu-advantage-tools into noble-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/32.3.1~24.04
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Craig, or anyone else affected,
Accepted torbrowser-launcher into noble-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/torbrowser-
launcher/0.3.7-1ubuntu1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Thanks for the upload as well.
Ideally, the version should be `0.3.7-1ubuntu0.1` (not `ubuntu1`), as this
is for stable release (see [1]), but in this case it's fine -- the version
hasn't been used (see [2]), and will not be used anymore, as devel release
is already at `0.3.7-2`.
Now, I'd
Thanks for mentioning that the proposed change is present in Firefox AppArmor
profiles.
Looking at its snap profiles, this can be traced back to snapd; that builds
confidence.
For documentation purposes:
$ sudo apt update && sudo apt install -y firefox
$ dpkg -s firefox | grep ^Description:
Marking Oracular as Fix Released.
torbrowser-launcher (0.3.7-2) unstable; urgency=medium
[ Daniel Rusek ]
* debian/patches:
- Add patch 05 to fix keyboard input issue.
...
** Changed in: torbrowser-launcher (Ubuntu Oracular)
Status: Invalid => Fix Released
--
You received this
Hello Erich, or anyone else affected,
Accepted ubuntustudio-installer into noble-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntustudio-installer/1.18.4 in a
few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Erich, or anyone else affected,
Accepted ubuntustudio-installer into noble-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntustudio-installer/1.18.4 in a
few hours, and then in the -proposed repository.
Please help us by testing this new
Tagging this bug as block-proposed-noble,
in addition to the request in comment #1.
aardvark-dns 1.6.0-1 (this upload) depends on netavark >> 1.6 [1],
which cannot be satisfied on ppc64el as netavark 1.6.0-1, that is
in noble-proposed FTBFS (build log [2]; see bug 2063447 comment 2),
and
** Description changed:
[Impact]
The links for the following are broken in the Service Information or the Host
Information menus for the following links:
View Trends For This Service
View Alert Histogram For This Service
View Trends For This Host
View Alert Histogram For This Host
Test Steps:
---
lxc launch ubuntu-daily:oracular nagios4-oracular
lxc exec nagios4-oracular -- su - ubuntu
sudo apt update
sudo apt install nagios4 apache2 --yes --no-install-recommends
sudo a2dismod mpm_event
sudo a2dismod mpm_worker
sudo a2enmod mpm_prefork
sudo a2enmod php8.3
sudo a2enmod
Hi Jorge,
Thanks for your work on the analysis and SRU bug template!
I checked this per your request, and we talked about it today.
So, just some notes for documentation purposes and next steps.
The proposed changed to `--with-cgiurl=` just works around the
issue, that is the links are broken
** Changed in: nagios4 (Ubuntu Oracular)
Status: In Progress => Incomplete
** Changed in: nagios4 (Ubuntu Noble)
Status: In Progress => Incomplete
** Changed in: nagios4 (Ubuntu Mantic)
Status: In Progress => Incomplete
** Changed in: nagios4 (Ubuntu Jammy)
Status:
Chengen,
Now the changes review notes:
This patch is concerning for a couple of reasons, if I understand correctly:
1) behavior changes that are potentially impactful to the storage backend;
2) new requirements for the deployment configuration that might seriously
impact the deployment.
In
Hi Chengen,
Thanks for your work on this bug / fix / SRU template!
Some process review notes:
In the future, please update the bug tasks for the newer/devel releases
as well.
In this case, Mantic not marked as Won't Fix possibly would require you
an extra round-trip during the review with the
** Also affects: cinder (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: cinder (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: cinder (Ubuntu Oracular)
Importance: Undecided
Status: New
** Changed in: cinder (Ubuntu Mantic)
** Description changed:
[Impact]
Deleting a volume will fail if it has snapshot or volume children, resulting
in an ImageBusy error.
[Fix]
Upstream has a patch that uses RBD flatten operations to break dependencies
between volumes and snapshots, reducing failures when using RBD
** Description changed:
[Impact]
Deleting a volume will fail if it has snapshot or volume children, resulting
in an ImageBusy error.
[Fix]
Upstream has a patch that uses RBD flatten operations to break dependencies
between volumes and snapshots, reducing failures when using RBD
Flipping the verification tags as requested in comment 65,
based on feedback from comments 70, 68, and 66.
(The other issue mentioned in comment 66 seems unrelated,
and might just be something else now that the package is
able to start services at all, and thus hit other issues.)
Retried the
The vendorized asyncore.py is identical in python3-pyasyncore (main).
It's better to rely on the package (vs. vendoring) for the stable release,
specially for an LTS, where ESM is 10-12 years, to avoid code duplication
and monitoring/patching on potential security vulnerabilities in 2 places.
/ubuntu/lp1988366
** Changed in: python-rtslib-fb (Ubuntu Jammy)
Status: Incomplete => Triaged
** Changed in: python-rtslib-fb (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: python-rtslib-fb (Ubuntu Jammy)
Assignee: (unassigned) => Mauricio Faria de Oliv
Changed in: gcc-9 (Ubuntu Jammy)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: gcc-9 (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: gcc-9 (Ubuntu Focal)
Status: New => Triaged
** Changed in: gcc-9 (Ubuntu Focal)
Assigne
Similarly for gcc-9 (9.5.0-6 in Noble/Oracular).
gcc-9 (9.5.0-6) unstable; urgency=medium
* Address stack protector and stack clash protection weaknesses
on AArch64. CVE-2023-4039.
$ rmadison -a source gcc-9
gcc-9 | 9.3.0-10ubuntu2| focal | source
gcc-9 |
Similarly for gcc-10 (10.5.0-4 in Noble/Oracular).
gcc-10 (10.5.0-4) unstable; urgency=medium
* Fix ftbfs on AArch64 in previous upload.
gcc-10 (10.5.0-3) unstable; urgency=medium
* Address stack protector and stack clash protection weaknesses
on AArch64. CVE-2023-4039. Taken from the
Similarly for gcc-11 (11.4.0-4 in Mantic/Noble/Oracular).
gcc-11 (11.4.0-4) unstable; urgency=medium
- Address stack protector and stack clash protection weaknesses
on AArch64. CVE-2023-4039.
$ rmadison -a source gcc-11
gcc-11 | 11.2.0-19ubuntu1 | jammy | source
gcc-12 fixed in 12.3.0-9, already in Mantic/Noble/Oracular (devel).
gcc-12 (12.3.0-9) unstable; urgency=medium
- Address stack protector and stack clash protection weaknesses
on AArch64. CVE-2023-4039.
$ rmadison -a source gcc-12
gcc-12 | 12-20220319-1ubuntu1 | jammy |
Apparently, cannot target gcc-9 to Jammy/Focal, not even by going to the
edit status link/page manually.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054343
Title:
CVE-2023-4039: ARM64 GCC
To
)
Importance: Undecided => Medium
** Changed in: gcc-12 (Ubuntu Jammy)
Status: New => Triaged
** Changed in: gcc-12 (Ubuntu Jammy)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: gcc-11 (Ubuntu Jammy)
Importance: Undecided => Medium
** Change
From ubuntu-ser...@lists.ubuntu.com:
On Thu, Jun 6, 2024 at 11:31 AM Paride Legovini wrote:
> # https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/2068529
> # Focal: Reverse proxy POST with with body length >1000 is missing body
>
> The bug comes from SEG, so I asked for clarification on
ns from the server team are. I also asked a couple of
> questions on the bug itself, and set it to Incomplete.
Thanks for the triage, Paride!
Just to clarify: I looked this up, and this bug doesn't come from SEG.
Please feel free to handle it. I clarified this in more detail in the bug.
cheers
The 2 autopkgtests failures above are infrastructure issues (both on armhf).
I'll retry them in a while.
0s : failure: ['lxc', 'launch', '--ephemeral', ...] failed (exit
status 1, stderr 'Error: The remote "..." doesn\'t exist\n')
0s autopkgtest [18:16:45]: ERROR: testbed failure: unexpected
Uploaded to Focal.
Build-tested on PPA [1] with -proposed enabled.
[1] https://launchpad.net/~mfo/+archive/ubuntu/horizon-
lp1728031-lp2054799-lp2055409/
** Changed in: horizon (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: horizon (Ubuntu Focal)
Status: New => In
Uploaded to Jammy.
Build-tested on PPA [1] with -proposed enabled.
[1] https://launchpad.net/~mfo/+archive/ubuntu/horizon-
lp1728031-lp2054799-lp2055409/
** Changed in: horizon (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: horizon (Ubuntu Jammy)
Status: New => In
Uploaded to Jammy.
Build-tested on PPA [1] with -proposed enabled.
[1] https://launchpad.net/~mfo/+archive/ubuntu/horizon-
lp1728031-lp2054799-lp2055409/
** Changed in: horizon (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: horizon (Ubuntu Jammy)
Status: New => In
Uploaded to Jammy.
Build-tested on PPA [1] with -proposed enabled.
[1] https://launchpad.net/~mfo/+archive/ubuntu/horizon-
lp1728031-lp2054799-lp2055409/
** Changed in: horizon (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: horizon (Ubuntu Jammy)
Status: New => In
Uploaded to Mantic.
Build-tested on PPA [1] with -proposed enabled.
[1] https://launchpad.net/~mfo/+archive/ubuntu/horizon-
lp1728031-lp2054799-lp2055409/
** Changed in: horizon (Ubuntu Mantic)
Importance: Undecided => Medium
** Changed in: horizon (Ubuntu Mantic)
Status: New => In
Robie (comment #35),
Good point; I added that to the Test Plan section to be safe.
Even if that's already covered in automated testing, glitches
or regressions in the web UI, if any, would likely be quickly
spot by humans, despite passing tests.
Thanks!
** Description changed:
After
Uploaded to Mantic.
Build-tested on PPA [1] with -proposed enabled.
[1] https://launchpad.net/~mfo/+archive/ubuntu/horizon-
lp1728031-lp2054799-lp2055409/
** Changed in: horizon (Ubuntu Mantic)
Importance: Undecided => Medium
** Changed in: horizon (Ubuntu Mantic)
Status: New => In
Uploaded to Mantic.
Build-tested on PPA [1] with -proposed enabled.
[1] https://launchpad.net/~mfo/+archive/ubuntu/horizon-
lp1728031-lp2054799-lp2055409/
** Changed in: horizon (Ubuntu Mantic)
Importance: Undecided => Medium
** Changed in: horizon (Ubuntu Mantic)
Status: New => In
Slightly reformatted the Impact section and clarified the behavior
change/extension with the opt-in config.
** Description changed:
Setting the config option OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES to
False successfully allows skipping neutron calls when loading the
instance list page,
Uploaded to Noble.
** Changed in: horizon (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: horizon (Ubuntu Noble)
Status: New => In Progress
** Changed in: horizon (Ubuntu Noble)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
--
You received
Uploaded to Noble.
** Changed in: horizon (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: horizon (Ubuntu Noble)
Status: New => In Progress
** Changed in: horizon (Ubuntu Noble)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
--
You received
** Description changed:
After following the security hardening guidelines:
https://docs.openstack.org/security-guide/dashboard/checklist.html#check-dashboard-09-is-enforce-password-check-set-to-true
After this check is enabled
Check-Dashboard-09: Is ENFORCE_PASSWORD_CHECK set to True
Removed subscription of ubuntu-sponsors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054390
Title:
Refine proc mounts entries traversal
To manage notifications about this bug go to:
No, please ignore it for now; there's an issue/regression identified in
the patch.
** Changed in: cryptsetup (Ubuntu Noble)
Status: In Progress => Incomplete
** Changed in: cryptsetup (Ubuntu Mantic)
Status: In Progress => Incomplete
** Changed in: cryptsetup (Ubuntu Jammy)
Fix Committed in oracular-proposed (horizon 4:24.0.0-0ubuntu2) [1].
Waiting on proposed-migration to oracular (mostly autopkgtests) [2].
If all goes well with oracular/development release, I will proceed
with review/sponsorship to the stable releses (I can handle those).
[1]
Fix Committed in oracular-proposed (horizon 4:24.0.0-0ubuntu2) [1].
Waiting on proposed-migration to oracular (mostly autopkgtests) [2].
If all goes well with oracular/development release, I will proceed
with review/sponsorship to the stable releses (I can handle those).
[1]
** Description changed:
[Impact]
We are not able to see the list of users and groups assigned to a
project in Horizon.
[Test Case]
Please refer to [Test steps] section below.
[Regression Potential]
The fix ed768ab is already in the upstream main, stable/2024.1,
** Changed in: horizon (Ubuntu Oracular)
Importance: Undecided => Medium
** Changed in: horizon (Ubuntu Oracular)
Status: New => Triaged
** Changed in: horizon (Ubuntu Oracular)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
--
You received this bug notification be
** Changed in: horizon (Ubuntu Oracular)
Importance: Undecided => Medium
** Changed in: horizon (Ubuntu Oracular)
Status: New => Triaged
** Changed in: horizon (Ubuntu Oracular)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
--
You received this bug notification be
Marking as verification done for noble per comments 25, 26, 30, and 31
(requested in comment 24). Thanks!
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
--
You received this bug notification because you are a member of
Paolo, thanks for the upload to oracular.
This is now just pending the regular verification of noble-proposed
(comment #4).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063820
Title:
Hi Björn,
> @Mauricio as you can see the qemu version 6.2 is used in RHEL 8.5 too.
> They integrated this patch two years ago. The QEMU project has this patch
> since version 7.0.
> I think it is well tested.
Thanks for the reassurance of the code _change_ testing in RHEL and
upstream!
This
Sergio, thanks for the updates to the bug description/SRU template.
I've extended the Test Plan to cover not only boots, but reboots too,
of course, which the patch changes/exercises (missed this previously);
and Regression Potential, to point to the modified area (cpu reset).
** Description
Hello Björn, or anyone else affected,
Accepted qemu into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/qemu/1:6.2+dfsg-2ubuntu6.20 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Frode, or anyone else affected,
Accepted openvswitch into noble-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/openvswitch/3.3.0-1ubuntu3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Frode, or anyone else affected,
Accepted openvswitch into noble-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/openvswitch/3.3.0-1ubuntu3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Frode, or anyone else affected,
Accepted openvswitch into noble-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/openvswitch/3.3.0-1ubuntu3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Review feedback:
- Versioning:
It's standard practice that version string for stable releases are
incremented by `ubuntu0.1`, and development release, by `ubuntu1`
(please see [1]).
This SRU/upload incremented by `ubuntu1`, but this was accepted
previously (noble: ubuntu1, noble-proposed:
Added to the 'Regression Potential' an statement along the lines of the
intended meaning 'Where problems could occur' [3], which relates to
where/what the patch changes.
Please amend/correct in case I missed something/misunderstood the patch;
thanks!
[3]
Marking devel/oracular as Fix Released (patch included):
$ pull-lp-source openvswitch
Found openvswitch 3.3.0-5 in oracular
...
$ cd openvswitch-3.3.0
$ grep 'ofproto-dpif - continuation with meters' tests/ofproto-dpif.at
AT_SETUP([ofproto-dpif - continuation with meters])
$ grep -A6
This is arguably a reasonable combination (although with slight differences)
of 'FTBFS' and 'Autopkgtest failures' (i.e., 'for successful build/test run')
acceptable per SRU policy (included below), thus should not need staging.
And even though this SRU (openvswitch) is directed at
** Description changed:
[Impact]
This release sports mostly bug-fixes and we would like to make sure all of our
supported customers have access to these improvements.
The update contains the following package updates:
-* ovn 24.03.2
+ * ovn 24.03.2
[Test Case]
The
Clarified/added '(Bug 2066908: [SRU] ovn 24.03.2 point release)' in the
Impact section.
** Description changed:
[ Impact ]
There is a bug in Open vSwitch which is required for successful build and
test run for OVN 24.03.2.
+ (Bug 2066908: [SRU] ovn 24.03.2 point release)
[ Test plan ]
For doc purposes (please clarify the tag change in the future, if at all
possible :)
`removed: block-proposed-noble`, see openvswitch 3.3.0-1ubuntu3
(including 3.3.0-1ubuntu2 above) in noble's unapproved queue; bug
2066906.
--
You received this bug notification because you are a member of
For doc purposes (please clarify the tag change in the future, if at all
possible :)
`removed: block-proposed-noble`, see openvswitch 3.3.0-1ubuntu3
(including 3.3.0-1ubuntu2 above) in noble's unapproved queue; bug
2066906.
--
You received this bug notification because you are a member of
SRU team:
The upload in noble's unapproved queue (ovn 24.03.2-0ubuntu0.24.04.1)
should only be accepted _after_ the openvswitch SRU for bug 2066906
is accepted, built, and available in noble-proposed (build-time dep):
Per bug 2066906:
'There is a bug in Open vSwitch which is required for
Hi Simon,
Just following up on this bug's failed verification (per above).
Could you please clarify the next steps, when you have a chance?
(e.g., an incremental fix to noble-proposed will be uploaded,
or maybe the existing fix in noble-proposed should be removed
if that may not happen soon; or
Verification still pending for noble-proposed
(blocks combined SRU release for bugs 2059818/done, 2059819/done,
2042844/needed)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2042844
Title:
JS
Adding bug task for Noble in Fix Committed as it's in noble-proposed
(likewise for Oracular).
$ rmadison -a source aardvark-dns | grep -e oracular -e noble
aardvark-dns | 1.4.0-5| noble/universe | source
aardvark-dns | 1.4.0-5| oracular/universe | source
Autopkgtests for oracular/cockpit/s390x passed with a retry,
that should unblock the oracular-proposed migration shortly.
316-1build1 sosreport/4.7.0-0ubuntu12024-05-22
15:19:06 UTC 0h 04m 29s mfo pass
1bc3dca3-467e-430b-b336-fe8c1f19b6d5
--
You received
The autopkgtests failures for mantic/jammy/focal have cleared up with retries.
Proceeding with the release of these series.
lintian [mantic/armhf]
2.116.3ubuntu3.2lintian/2.116.3ubuntu3.2
2024-05-20 22:46:45 UTC 0h 32m 13s mfo pass
The verification for noble/mantic/jammy/focal look good; thanks!
However, the autopkgtests failures for mantic/jammy/focal aren't clear.
I retried them, as apparently they are infrastructure related timeouts/issues.
I'll check later if still on shift.
--
You received this bug notification
The verification of the Stable Release Update for lintian 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
The verification of the Stable Release Update for nbd 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
Verificaton done on noble-proposed.
Thanks for the detailed test steps!
(I updated the last command from 'nbd-client -d nbd0' to 'nbd-client nbd0',
which reflects the test step without the fix, in 'Now, trigger the problem').
Environment:
---
lxc launch ubuntu:noble --vm mfo-noble-vm
lxc shell
1 - 100 of 1860 matches
Mail list logo
