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 Pro
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 followin
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 Pro
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 Pro
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, the
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
Th
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:
https://bugs
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] https://launchpad.ne
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] https://launchpad.ne
** 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,
stabl
** 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 Ubun
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:
rtl8812au-dk
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 is
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 chan
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
https://w
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
htt
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
htt
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
htt
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: ubuntu
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] https://wiki.ubuntu.com/StableReleaseUpdat
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 '^put_contr
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 fixing/preventi
** 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 follo
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 Ubuntu
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 Ubuntu
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 successf
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 t
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 ERROR
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
aar
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 this
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
ef36
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 becaus
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 regr
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 m
** Description changed:
[ Impact ]
nbdtab uses a port of 0 by default which is not sensible. This means
that if you do not set a default port in nbdtab, it will fail.
You will see an error such as: Error: Socket failed: Connection refused
[ Test Plan ]
$ lxc launch ubuntu:n
This SRU is blocked on the upload to the Development Release, as per [1]
(comment #2).
If that is not possible or needed, please explain. Marking Oracular as
Incomplete. Thanks!
[1]
https://wiki.ubuntu.com/StableReleaseUpdates#Development_Release_Fixed_First
** Changed in: rtl8812au (Ubuntu Ora
The verification of the Stable Release Update for remmina 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
Marking this SRU as verification-failed per comments
- #4 (partial failure with applications running) and
- #5 (failure even without applications running).
The partial failure would seem like a regression too,
since the bug description says that the fix / change
acts 'effectively and immediately'
Verification pending for noble-proposed
(blocks combined SRU release for bugs 2059818, 2059819, 2042844)
--
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 ERROR: Gio.DBusError:
GDBus
Verification pending for noble-proposed
(blocks combined SRU release for bugs 2059818, 2059819, 2042844)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059819
Title:
Regression: Jammy to Noble, righ
This SRU is pending verification for noble-proposed and autopkgtests
regressions to be cleared up.
I looked the autopkgtests regressions, and some seem to be temporary
conditions on the infrastructure, thus I just triggered retries for all
tests/archs.
--
You received this bug notification becau
This SRU is pending clarification about the verification tags flip
(comments 23, 12, 7) and other questions (comment 23).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061747
Title:
obsolete out-of
Attaching the error image linked in the bug description for archival
purposes:
"""
Expectation: Get a table with the users assigned to this project.
Result: Get an error - https://i.imgur.com/TminwUy.png [attached]
"""
** Attachment added: "TminwUy.png"
https://bugs.launchpad.net/ubuntu/+sour
Commit ed768ab50713 (proposed for Ubuntu SRUs & Cloud Archive) isn't in
Oracular yet, IIUIC; adding bug task.
master
$ git log --oneline -1 ed768ab
ed768ab50713 Fix Users/Groups tab list when a domain context is set
stable/2024.1
$ git log --oneline origin/stable/2024.1
Adding bug tasks for Noble/Oracular as Fix Released, for clarity, per
comment #2 and checks below.
$ git log --oneline -1 95089025fda7c8cce6f7195e2a63f7f09efc9e0a
95089025fda7 Extend configurable skippability of neutron calls to project
instance detail
$ git describe --contains 95089025fda7
24.0
Patch [1] (proposed for Ubuntu SRUs & Cloud Archive) isn't in
Oracular/Noble yet, IIUIC; adding bug tasks.
$ git log --oneline -- openstack_dashboard/api/keystone.py | grep -m1
'Fix error on changing user password by admin'
da8e95929857 Fix error on changing user password by admin
Marking Bionic as Won't Fix as it's End of Standard Support (EOSS), and in
Expanded Security Maintenance (ESM).
If you have an Ubuntu Pro subscription with Support, and would like a fix,
please open a support ticket.
** Tags removed: sts-sponsor-volunteer
** Changed in: kmod (Ubuntu Bionic)
** Tags removed: sts-sponsor-volunteer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875669
Title:
autopkgtest failures
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubu
Oh, and Oracular indeed just migrated while I posted the comment (#21
#22); nice timing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064580
Title:
Please update the package to 20240320.00
To man
The verification of the Stable Release Update for google-osconfig-agent
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 y
Summary for SRU release.
Autopkgtests: OK
- Devel/O: proposed migration was blocked in a test queued since early May;
re-triggered it and it passed; this should migrate soon.
- Stable/NMJF: re-triggered/cleared autopkgtests pending; all series/archs
passed.
Builds/FTBFS: OK
- Focal/riscv64: fai
Hi Robie, Sergio,
The concern about removing 'version_attributes' and 'discovery_auth_attributes'
can be addressed with this simple change/backport.
What do you think?
Don't remove the 2 attributes / move elements into 'target_name_excloudes'.
Instead, add a new attribute / its element into 'ta
To be clear, I don't think these should block the acceptance of this SRU
(I have seen different criteria to accept SRUs regarding DEP-3 headers),
but hopefully might be of some value for future SRUs, if you agree w/ it.
I'll refrain from accepting it for now as oracular-proposed seems to have
some
Hi Dave (~waveform),
Thanks for all the work to review/sponsor this fix! (And several others!)
It's really appreciated.
In a comparatively small but relevant note, I'd like to humbly point out though
that some DEP-3 headers seem incorrect (IMHO) in the uploads AFAICT based in [1]
(section `Standa
Rejected from the unapproved queues for Noble, Mantic, Jammy, and Focal
per comment #14. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921914
Title:
[SRU] package quickml 0.7-5.1 failed to
Hi Sergio,
Thanks for the upload!
The bug and fix sound good and relatively simple to verify.
The SRU bug template is still missing Test Plan / Regression Potential,
so I'll mark it as Incomplete for the time being (I see it may be coming
soon, per "TBD").
While looking at the Björn's mention o
Chlo, thanks for the updates to the SRU template.
'Where problems could occur' is indeed generic as can be expected for
such a big update, but the information there is certainly helpful.
The one point/patch that applies to Ubuntu more directly in the big update
(comment #5)
is a gpg/apt change [
Hi Utkarsh,
Thanks for the pointer to the dependency changes as requested by the SRU
exception, and update to the bug template.
I had seen that in the diff (and filter it out, per the size, of
course), but I think what the request in the SRU exception is, is
something easier to parse re: the vers
Hello Philip, or anyone else affected,
Accepted google-osconfig-agent into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/google-osconfig-
agent/20240320.00-0ubuntu1~22.04.0 in a few hours, and then in the
-proposed repository.
Please help us b
Hello Philip, or anyone else affected,
Accepted google-osconfig-agent into focal-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/google-osconfig-
agent/20240320.00-0ubuntu1~20.04.0 in a few hours, and then in the
-proposed repository.
Please help us b
The uploads for Jammy and Focal follow Oracular's too,
with additional changes to use a newer go version, as
already done in Focal (J: any > 1.21; F: 1.18 > 1.21).
Please address the SRU-related requests in comment #7.
Thanks!
** Changed in: google-osconfig-agent (Ubuntu Jammy)
Status: Ne
The uploads for Noble and Mantic follow Oracular's as expected (#5),
the only differences being timestamps and a securiy patch in Mantic.
The code changes look good AFAICT, and the vendored deps changes
are such in size that require validation by testing.
Please address the request in comment #6
Hello Philip, or anyone else affected,
Accepted google-osconfig-agent into mantic-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/google-osconfig-
agent/20240320.00-0ubuntu1~23.10.0 in a few hours, and then in the
-proposed repository.
Please help us
Hello Philip, or anyone else affected,
Accepted google-osconfig-agent into noble-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/google-osconfig-
agent/20240320.00-0ubuntu1~24.04.0 in a few hours, and then in the
-proposed repository.
Please help us b
It looks like the uploads are coming in
(noble 25 mins ago, mantic 16 mins ago).
After your code/package-wise tasks are done,
could you please take a look at listing the
vendorized deps changes, as per SRU exception?
I realize that might be a lot, but it's in the
exception, so it must be asked f
Updating the Oracular bug task to Fix Committed, as the
reference to this bug is already in oracular-proposed [1].
The Oracular Oriole (active development)
20240320.00-0ubuntu1proposed (main) 9 hours ago
Changelog
google-osconfig-agent (20240320.00-0ubuntu1) o
This bug received a prioritization request for SRU review.
Unfortunately, apparently the uploads for stable releases
haven't happened today so far (but I will check tomorrow).
Meanwhile, I have familiarized myself with the upload for
Oracular, which is expected to be quite similar to stable
relea
Hi Jorge,
Thanks for testing and the update.
Re: mantic-proposed, that is weird; any mirrors in place? It looks OK in the
archive:
(All cinder binary packages were available in the verification of bug 1987663.)
$ curl -s
http://archive.ubuntu.com/ubuntu/dists/mantic-proposed/main/binary-amd64/
Hi Timo,
Thanks for looking into this.
> Wouldn't it be less risky to just backport 8.0.4 instead of 24/36
commits to mantic/jammy?
So so; and there's more involved.
There are near-future steps being taken in that direction already (SRU
exception to be discussed in the upcoming Engineering Spri
Hi Jorge,
Thanks for verifying jammy-proposed.
Could you please verify mantic-proposed as well?
The fix release to jammy-updates depends on release for mantic-updates (ie,
verification of mantic-proposed).
Thanks again!
--
You received this bug notification because you are a member of Ubuntu
Verification done on {mantic,jammy,focal}-proposed.
The detailed verification steps as per comment #3
are attached. This is the summary with key steps.
With the packages from -proposed, when (re)starting
{cinder-volume,tgt}.service,
the cinder-volume service is started _after_ the tgt service,
The updates look good, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063221
Title:
Drop libglib2.0-0 transitional package
To manage notifications about this bug go to:
https://bugs.launchp
** Changed in: rustc (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052985
Title:
[SRU] Upgrade Rust to 1.76.0
To manage notifications about this bug go to
Hi Jeremy,
This looks mostly good, AFAICT.
Could you please complete the SRU bug template by adding the section
'Where problems could occur' / 'Regression potential'? [1]
And although the 'Test Case' is feasible to understand, based on the 'Impact'
section, it would be nice to have a 'functiona
I tested this with a local package build and local repo in a mantic container,
doing an `apt --dry-run dist-upgrade` without/with that repo (w/ noble apt
sources list),
and manually download/run noble's release upgrader without/with that repo.
The behavior is the same (ie, no regressions) as expe
Ok; thanks for clarifying.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061891
Title:
Noble upgrade breaks iptables-persistent and netfilter-persistent
usage
To manage notifications about this
Moving from Fix Committed back to In Progress as this isn't in -proposed yet,
and In Progress reflects 'uploaded' better.
(I don't mean to be pedantic, but this avoids confusion; even though the git
repo was mentioned, AFAIK the 'Ubuntu' project in bug tasks means the status
Fix Committed should b
Moving from Fix Committed back to In Progress as this isn't in -proposed yet,
and In Progress reflects 'uploaded' better.
(I don't mean to be pedantic, but this avoids confusion; even though the git
repo was mentioned, AFAIK the 'Ubuntu' project in bug tasks means the status
Fix Committed should b
Hi Nick and Julian,
Thanks for the fix and SRU template!
Question:
IIUIC, the fix simply removes 'ufw' if '{iptables,netfilter}-persistent'
is installed.
But is it possible that removing ufw is the wrong thing to do in some
particular case?
Say, if the user actually used/configured ufw inste
** Description changed:
- [Impact / Original Description]
+ [Impact]
+ ufw and -persistent packages both manage the firewall, hence they conflict
but they accidentally had no conflicts in jammy. If both are installed,
persistent packages will store and restore firewall configuration, so ufw
can
Updating the verification tags for the new version,
agreeing with Christian's assessment in comment 12,
and verifying that the changes are still included:
$ pull-lp-debs -a arm64 libvirt-daemon-system focal 6.0.0-0ubuntu8.20
$ dpkg-deb -x libvirt-daemon-system_6.0.0-0ubuntu8.20_arm64.deb deb
$ fgr
The packages in focal-proposed have also been verified successfully in
real-world/non-synthetic tests by one of our Ubuntu Pro support
customers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059272
Verification done on focal-proposed, following comments 23, 24, 25, 26.
Including in this comment a few key snippets from each test/comment.
---
Environment
---
LXD virtual machine
lxc launch --vm ubuntu:focal lp2059272-focal
lxc exec lp2059272-focal -- su - ubuntu
Enable proposed & debug sy
(unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: qemu (Ubuntu)
Assignee: Sergio Durigan Junior (sergiodj) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048517
Ti
Hi Giuseppe,
Please test nova version 2:21.2.4-0ubuntu2.7~ppa3 in the PPA.
(It's finished building and should be published in some time.)
The config change should be something along the lines of
`cpu_model_extra_flags = -xsaves`
I couldn't test the package/functionality yet, but all of the
bui
Hmm, sorry, please hold; the unit tests caught an error.
I'll check that on Monday.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048517
Title:
EPYC-Rome model without XSAVES may break live migrati
Mantic and Jammy built successfully in all supported architectures.
(riscv64 fails, but it also fails on mantic/jammy-release; it's OK.)
Uploaded!
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Hi Giuseppe,
You're right, libvirt checks the specified model against its known
models.
However, the EPYC-Rome (not-v4) doesn't specify 'xsaves', just EPYC-Milan,
so it _seems_ the feature came from the default with cpu_model host-model,
which perhaps found EPYC Milan model closer to the host fla
** Description changed:
[Impact]
- Linux kernel 6.2 includes patches with structural changes that may render the
crash utility unable to parse the dump file.
+ Linux kernel 6.2 includes patches with structural changes that may render the
crash utility in Mantic (release kernel 6.5) and Jammy (
Jammy: patches 0001-0012 look good too!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2038249
Title:
The dump file parsing issue arises from structural changes in Linux
kernel 6.2
To manage notif
Partial review of the Jammy debdiff.
(Still in progress.)
Started with Jammy's patches 0012-0036, which are Mantic's patches 0001-0024
(already reviewed).
Most patches are identical, and some have context-line changes, as expected
(8.0.2/8.0.0 delta).
Just had a few changes.
$ for ((i=1; i<=24;
Today, I tackled the Mantic debdiff (made only a few changes; below).
It's now currently building in a PPA for all supported architectures,
(ppa:mfo/lp2038249) and if all goes well I will upload it to Mantic.
Thanks!
Mauricio
---
All 24 commits are included in Noble (12 in 8.0.4 and 12 in 8.0.3
** Description changed:
[Impact]
Linux kernel 6.2 includes patches with structural changes that may render the
crash utility unable to parse the dump file.
==
d122019bf061 mm: Split slab into its own type
401fb12c68c2 mm: Differentiate struct slab fields by sl*b implementations
201 - 300 of 1846 matches
Mail list logo
