Thanks, Lukas!
I rejected/reuploaded (now I had time :) the combined changes with
version 2.9 (as this has not yet been used in the archive).
The delta from 2.8 seen in the queue might be an effect of it not
considering -security, I guess; it isn't re-included in the upload.
This should be good
rebased on top of the pending nova upload. re-uploaded as a combined fix
on focal in 21.2.4-0ubuntu2.10
I dropped the security debdiff from 21.2.4-0ubuntu2.8 as those are
already included in focal-updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The nova upload for Focal has been rejected as it does not include the pending
nova upload in the unapproved queue.
Please either re-upload them combined or rebase this upload on top of that
after it is in -proposed.
Thanks!
--
You received this bug notification because you are a member of
Same story with Focal. Both sponsored.
https://launchpad.net/ubuntu/jammy/+queue?queue_state=1_text=nova
https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=nova
I'm now unsubscribing ~ubuntu-sponsors
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I can confirm the patch is included in Noble, via new upstream snapshot
in 3:27.1.0+git2023071215.f7ce4df5-0ubuntu1
Also, the backported patch matches the upstream logic of
https://opendev.org/openstack/nova/commit/697fa3c000696da559e52b664c04cbd8d261c037
Backported changes are documented in the
Noble 3:29.0.1-0ubuntu1.3 already contains the patch, so no changes are
needed.
** Changed in: nova (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
What is the status of this bug in noble? It needs to be resolved for
noble before we can SRU it to jammy and focal.
** Changed in: nova (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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
The attachment "lp2024258-nova-focal.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff. If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch"
Debdiff for Jammy
** Patch added: "lp2024258-nova-jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/2024258/+attachment/5783538/+files/lp2024258-nova-jammy.debdiff
** Changed in: nova (Ubuntu Focal)
Status: New => In Progress
** Changed in: nova (Ubuntu Jammy)
Debdiff for Focal
** Description changed:
- Observed downstream in a large scale cluster with constant create/delete
- server activity and hundreds of thousands of deleted instances rows.
+ [Impact]
+ Originally, Nova archives deleted rows in batches consisting of a maximum
number of parent
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nova (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: nova (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
12 matches
Mail list logo
