[Bug 2064580] Please test proposed package

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

[Bug 2064580] Please test proposed package

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

[Bug 2064580] Re: Please update the package to 20240320.00

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:

[Bug 2064580] Re: Please update the package to 20240320.00

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

[Bug 2064580] Please test proposed package

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

[Bug 2064580] Please test proposed package

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

[Bug 2064580] Re: Please update the package to 20240320.00

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

[Bug 2064580] Re: Please update the package to 20240320.00

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)

[Bug 2064580] Re: Please update the package to 20240320.00

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

[Bug 1988942] Re: Failed to set image property. Invalid input for field/attribute simplestreams_metadata. Value: ... is too long (HTTP 400)

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

[Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

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

[Bug 1988942] Re: Failed to set image property. Invalid input for field/attribute simplestreams_metadata. Value: ... is too long (HTTP 400)

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

[Bug 1987663] Re: cinder-volume: "Failed to re-export volume, setting to ERROR" with "tgtadm: failed to send request hdr to tgt daemon, Transport endpoint is not connected" on service startup

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,

[Bug 2063221] Re: Drop libglib2.0-0 transitional package

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:

[Bug 2052985] Re: [SRU] Upgrade Rust to 1.76.0

** 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

[Bug 2063221] Re: Drop libglib2.0-0 transitional package

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

[Bug 2063221] Re: Drop libglib2.0-0 transitional package

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

[Bug 2061891] Re: Noble upgrade breaks iptables-persistent and netfilter-persistent usage

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

[Bug 2063464] Re: systemd-resolved wasn't installed on upgrade from Jammy to Noble

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

[Bug 2064090] Re: Automatically installed bit not transitioned to t64 libraries

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

[Bug 2061891] Re: Noble upgrade breaks iptables-persistent and netfilter-persistent usage

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

[Bug 2061891] Re: Noble upgrade breaks iptables-persistent and netfilter-persistent usage

** 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

[Bug 1989078] Re: libvirt-qemu apparmor profile doesn't allow locking of AAVMF firmware

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 $

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

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

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

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

[Bug 2048517] Re: EPYC-Rome model without XSAVES may break live migration since the removal of the flag on the physical CPU

gt; 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 Title: EPYC-Rom

[Bug 2048517] Re: EPYC-Rome model without XSAVES may break live migration since the removal of the flag on the physical CPU

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

[Bug 2048517] Re: EPYC-Rome model without XSAVES may break live migration since the removal of the flag on the physical CPU

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

[Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

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.

[Bug 2048517] Re: EPYC-Rome model without XSAVES may break live migration since the removal of the flag on the physical CPU

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

[Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

** 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

[Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

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

[Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

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;

[Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

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

[Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

** 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

[Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

Marking Lunar as Won't Fix (EOL). -- 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

[Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

crash 8.0.4 is available in noble (bug 2047861); checking the stable releases' debdiffs. ** Changed in: crash (Ubuntu Noble) Status: Fix Committed => Fix Released ** Description changed: [Impact] Linux kernel 6.2 includes patches with structural changes that may render the crash

[Bug 2038249] Re: The dump file parsing issue arises from structural changes in Linux kernel 6.2

Updated the SRU template as requested in comment #11 with the detailed test plans provided in comments #16-#20. ** Changed in: crash (Ubuntu Lunar) Status: In Progress => Won't Fix ** Changed in: crash (Ubuntu Lunar) Importance: Medium => Undecided ** Changed in: crash (Ubuntu Lunar)

[Bug 1987663] Re: cinder-volume: "Failed to re-export volume, setting to ERROR" with "tgtadm: failed to send request hdr to tgt daemon, Transport endpoint is not connected" on service startup

Cloud Archive: Caracal is addressed with Noble Bobcat is addressed with Mantic * Antelope is _not_ addressed with Lunar (no longer supported), needs patching in UCA [Triaged] Zed is no longer supported (2024/04) Yoga is addressed with Jammy Wallaby is no longer supported (2024/04) Victoria is no

[Bug 1988942] Re: Failed to set image property. Invalid input for field/attribute simplestreams_metadata. Value: ... is too long (HTTP 400)

Cloud Archive: Caracal is addressed with Noble Bobcat is addressed with Mantic * Antelope is _not_ addressed with Lunar (no longer supported), needs patching in UCA [Triaged] Zed is no longer supported (2024/04) Yoga is addressed with Jammy -- You received this bug notification because you are

[Bug 1994521] Re: HPE3PAR: Failing to clone a volume having children

Cloud Archive: Caracal is addressed with Noble Bobcat is addressed with Mantic * Antelope is _not_ addressed with Lunar (no longer supported), needs patching in UCA [Triaged] Zed is no longer supported (2024/04) Yoga is addressed with Jammy -- You received this bug notification because you are

[Bug 1987663] Re: cinder-volume: "Failed to re-export volume, setting to ERROR" with "tgtadm: failed to send request hdr to tgt daemon, Transport endpoint is not connected" on service startup

Uploaded to Mantic, Jammy, Focal. This upload has been coordinated with the Openstack Engineering team (~james-page) for bugs 1987663, 1988942, and 1994521. Test PPA and build-time unit test summary in https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1987663/comments/16 ** Changed in:

[Bug 1994521] Re: HPE3PAR: Failing to clone a volume having children

** Changed in: cinder (Ubuntu Jammy) Status: Incomplete => In Progress ** Changed in: cloud-archive/bobcat Status: New => Fix Released ** Changed in: cloud-archive/antelope Status: New => Triaged ** Changed in: cloud-archive/yoga Status: New => In Progress -- You

[Bug 1988942] Re: Failed to set image property. Invalid input for field/attribute simplestreams_metadata. Value: ... is too long (HTTP 400)

** Changed in: cloud-archive/antelope Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1988942 Title: Failed to set image property. Invalid input for

[Bug 1988942] Re: Failed to set image property. Invalid input for field/attribute simplestreams_metadata. Value: ... is too long (HTTP 400)

Uploaded to Mantic, Jammy. This upload has been coordinated with the Openstack Engineering team (~james-page) for bugs 1987663, 1988942, and 1994521. Test PPA and build-time unit test summary in https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1987663/comments/16 -- You received this

[Bug 1994521] Re: HPE3PAR: Failing to clone a volume having children

Uploaded to Jammy. This upload has been coordinated with the Openstack Engineering team (~james-page) for bugs 1987663, 1988942, and 1994521. Test PPA and build-time unit test summary in https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1987663/comments/16 -- You received this bug

[Bug 1994521] Re: HPE3PAR: Failing to clone a volume having children

Hi Seyeong, Thanks for the patches! In the future, could you please add DEP-3 headers [1] to them? (usually just 'Bug-Ubuntu:'/'Origin:' are needed on git patches) Also, it's a good practice to name the patch files with the bug prefix (this is style, not requirement, but it helps when there is

[Bug 1987663] Re: cinder-volume: "Failed to re-export volume, setting to ERROR" with "tgtadm: failed to send request hdr to tgt daemon, Transport endpoint is not connected" on service startup

The packages built successfully in Test PPA ppa:mfo/cinder- lp1987663-lp1988942-lp1994521 All build-time unit tests passed in the Test PPA (as in the Ubuntu Archive). Mantic: --- mantic-updates:

[Bug 1988942] Re: Failed to set image property. Invalid input for field/attribute simplestreams_metadata. Value: ... is too long (HTTP 400)

** Changed in: cloud-archive/zed Status: In Progress => Won't Fix ** Changed in: cloud-archive/zed Assignee: Jorge Merlino (jorge-merlino) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1987663] Re: cinder-volume: "Failed to re-export volume, setting to ERROR" with "tgtadm: failed to send request hdr to tgt daemon, Transport endpoint is not connected" on service startup

** Changed in: cloud-archive/wallaby Status: New => Won't Fix ** Changed in: cloud-archive/ussuri Status: New => Incomplete -- 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:

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

SRU team: this is on hold to double check the library symbols (thanks, Robie!), please do not accept yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059272 Title: libvirt domain is not

[Bug 1987663] Re: cinder-volume: "Failed to re-export volume, setting to ERROR" with "tgtadm: failed to send request hdr to tgt daemon, Transport endpoint is not connected" on service startup

Re: comment #13, I had re-tested Mantic, Jammy, and Focal with/without the patch (they all work/fail as expected), but forgot to update the bug. ** Changed in: cinder (Ubuntu Lunar) Importance: Medium => Undecided -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1994521] Re: HPE3PAR: Failing to clone a volume having children

Hey Seyeong, Dariusz, Thanks for the clarifications! Yes, this needs coordination with the Openstack Engineering team not only for the other changes they plan to combine in an upload, but also regarding the upstream acceptance situation for this in the different branches. Apparently, they still

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

Hi Sergio, Thanks for taking the time to read and review the patch and test cases! > this new code path could be reached even after the initialization, couldn't it? No, this code path should only be reached during initialization, AFAICT. That is because qemuProcessReconnect() can only be

[Bug 1976312] Please test proposed package

Hello thom, or anyone else affected, Accepted pathological into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pathological/1.1.3-16ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package.

[Bug 1976312] Re: [SRU] Pathological wont accept any input

Hi Sudip, Dave (uploader), Thanks for the patch for Ubuntu! These changes do not modify the DEP3 headers of the existing python3.patch file. For SRUs, it's good practice to add 'Bug-Ubuntu:' / 'Origin:' tags, and in the case the .patch file already exists, a 'Last-Update:' tag too would be

[Bug 1976312] Re: [SRU] Pathological wont accept any input

** Description changed: [ Impact ] pathological is completely unusable as none of the keyboard or mouse input will work. And the game can not be played if the user can not control the game. [ Test Plan ] 1. Install pathologial 2. Use up-down keys to check if different

[Bug 1936449] Please test proposed package

Hello DarkTrick, or anyone else affected, Accepted numptyphysics into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/numptyphysics/0.2+svn157-0.4ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new

[Bug 1936449] Re: [SRU] numptyphysics segfault on startup on XUb 21.04

Notes: - Version with the patch [0] (0.2+svn157-0.5) was introduced in Ubuntu on Impish [1] (older than Jammy in the SRU template, so updated the SRU template to increase version range it has been applied in Ubuntu). - The DEP-3 field 'Origin:' has an invalid optional prefix 'Debian'; it should

[Bug 1936449] Re: [SRU] numptyphysics segfault on startup on XUb 21.04

** Description changed: [ Impact ] numptyphysics is completely unusable as it will segfault immediately on start. [ Test Plan ] 1. Install numptyphysics 2. Start numptyphysics 3. Play the game to check it works If the package is not fixed then it will fail to start. -

[Bug 1994521] Re: HPE3PAR: Failing to clone a volume having children

Seyeong, Dariusz (subscribing you as you're the uploader), Could you please confirm whether the Openstack Engineering team is OK with the proposed changes, and that they are not upstream? From comment #12 it seems unclear whether the situation could move forward, and the SRU template was updated

[Bug 1970521] Please test proposed package

Hello Graham, or anyone else affected, Accepted boinc into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/boinc/7.18.1+dfsg-4ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1970521] Re: [SRU] boinc-client crashes when started with core dump on Xubuntu 22.04

Looked at potential performance regressions of removing AVX instructions. (Updated the SRU template sections accordingly.) The boinc packages do not provide high-performance code, it's the boinc _applications_ written to be run by the client and linked against the library for API access that

[Bug 1970521] Re: [SRU] boinc-client crashes when started with core dump on Xubuntu 22.04

** Description changed: [ Impact ] boinc-client is completely unusable on older CPU which does not have avx like a Celeron CPU. It will crash immediately if run on old CPU, but will run without any problem on newer CPUs. [ Test Plan ] It should be done on both types of CPUs,

[Bug 1970521] Re: [SRU] boinc-client crashes when started with core dump on Xubuntu 22.04

Marked bug 1988863 as a duplicate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970521 Title: [SRU] boinc-client crashes when started with core dump on Xubuntu 22.04 To manage notifications

[Bug 1988863] Re: boinc package uses avx instructions unconditionally

*** This bug is a duplicate of bug 1970521 *** https://bugs.launchpad.net/bugs/1970521 ** This bug has been marked a duplicate of bug 1970521 [SRU] boinc-client crashes when started with core dump on Xubuntu 22.04 -- You received this bug notification because you are a member of Ubuntu

[Bug 1892558] Please test proposed package

Hello Nathaniel, or anyone else affected, Accepted macutils into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/macutils/2.0b3-16ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1892558] Re: [SRU] binhex always segfaults

$ lsb_release -cs; dpkg -s macutils | grep ^Version:; dpkg -L macutils | grep /bin/ | while read BIN; do echo $BIN; $BIN -H >/dev/null 2>&1; echo RC = $?; done focal Version: 2.0b3-16build1 /usr/bin/binhex RC = 139 /usr/bin/frommac RC = 139 /usr/bin/hexbin RC = 0 /usr/bin/macsave RC = 0

[Bug 1892558] Re: [SRU] binhex always segfaults

Hi Sudip, Thanks for debugging, backporting, and submitting a patch! Nice touch on the DEP-3 headers. Just a style/cosmetic _suggestion_ that is helpful: in the future, please list the .patch file in d/changelog; e.g., '* d/p/fix-segfault.patch: Fix segfault with binhex, frommac and tomac. (LP:

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

Steps with test packages on Focal (shutdown-on-runtime) --- Stop libvirtd systemd units sudo systemctl stop 'libvirtd*' Start libvirt in GDB sudo gdb \ -iex 'set confirm off' \ -iex 'set pagination off' \ -ex 'set non-stop on' \ -ex 'handle SIGTERM nostop noprint

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

Steps with test packages on Focal (shutdown-on-init) --- Start test VM cat <<-EOF >test-vm.xml test-vm hvm 32 1 EOF virsh define test-vm.xml virsh start test-vm

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

Steps with test packages on Focal (normal restarts) --- Restart libvirt 100 times with 10 QEMU domains. All domains continued to be managed by libvirt. Create 10 test VMs (test-vm-1, test-vm-2, ..., test-vm-10): for NAME in test-vm-{1..10}; do cat <<-EOF >test-vms.xml && virsh define

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

Test packages with the new fix in ppa:mfo/lp2059272 built correctly in all supported architectures. The next 3 comments show steps to reproduce/verify the issue/fix with the test packages -- all passed. Environment --- LXD virtual machine lxc launch --vm ubuntu:focal lp2059272-focal

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

The new fix for shutdown-on-init on Focal is simpler: Skip the XML update on init if libvirt is shutting down. This is based on 2 points: 1) The XML update on initialization will not be used at all in this run of libvirtd, since libvirtd is shutting down. 2) The XML update in _this_

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

** Description changed: [ Impact ]  * If a race condition occurs on libvirtd shutdown,    a QEMU domain status XML (/run/libvirt/qemu/*.xml)    might lose the QEMU-driver specific information,    such as ''.    (The race condition details are in [Other Info].)  * On the next

[Bug 1988942] Re: Failed to set image property. Invalid input for field/attribute simplestreams_metadata. Value: ... is too long (HTTP 400)

Hi James; done! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1988942 Title: Failed to set image property. Invalid input for field/attribute simplestreams_metadata. Value: ... is too long (HTTP

[Bug 2038648] Re: package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade: installed sosreport package post-installation script subprocess returned error exit status 1

Hi Arif, Cool. So, the python version is a coordinated decision at the upstream project level -- that looks good. 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/2038648 Title:

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

(Un)fortunately, during focal-proposed testing today, a corner case was identified (late), which will require changes. Some of the qemuProcessReconnect() threads finished within the timeout but others didn't. The ones which didn't were waiting on a reply back from the QEMU monitor, but that

[Bug 2043983] Update Released

The verification of the Stable Release Update for ethtool 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

[Bug 2043983] Re: ethtool module info only reports hex info

Robie's requests in comment #25 are addressed, AFAICT. > Please could someone verify that the ethtool packages in jammy-proposed and > mantic-proposed > still work *on those respective releases*, and confirm the package versions > tested? > Once done, please flip the tags back. Thanks! The

[Bug 2042644] Update Released

The verification of the Stable Release Update for netdata 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

[Bug 2043983] Re: ethtool module info only reports hex info

** Attachment added: "lp2043983-verification-jammy-proposed.tar.xz" https://bugs.launchpad.net/ubuntu/+source/ethtool/+bug/2043983/+attachment/5761143/+files/lp2043983-verification-jammy-proposed.tar.xz ** Tags removed: verification-needed verification-needed-jammy ** Tags added:

[Bug 2043983] Re: ethtool module info only reports hex info

Verification done on jammy-proposed. Same output on non-affected interface type (e.g., 0x03, SFP), i.e., no regressions. Fixed output on affected interface type (i.e., 0x02, soldered), i.e., as expected. (* This has been verified by changing the type in GDB and checking output as below.)

[Bug 2043983] Re: ethtool module info only reports hex info

** Attachment added: "lp2043983-verification-mantic-proposed.tar.xz" https://bugs.launchpad.net/ubuntu/+source/ethtool/+bug/2043983/+attachment/5761142/+files/lp2043983-verification-mantic-proposed.tar.xz ** Tags removed: verification-needed-mantic ** Tags added: verification-done-mantic --

[Bug 2043983] Re: ethtool module info only reports hex info

Verification done on mantic-proposed. Same output on non-affected interface type (e.g., 0x03, SFP), i.e., no regressions. Fixed output on affected interface type (i.e., 0x02, soldered), i.e., as expected. (* This has been verified by changing the type in GDB and checking output as below.)

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

Thanks for the reviews, Sergio! That certainly helps building additional confidence in the patch. With that and tests covering all options (comments #13 and #15) showing good/expected results, I'm happy to upload it to Focal. ** Changed in: libvirt (Ubuntu Focal) Status: Confirmed => In

[Bug 2042644] Re: netdata-web 1.42.1 is inaccessible

The previous comment confirmed the package in -proposed works, but didn't flip the verification tag. I also performed a quick verification (thanks for the test plan), and it looks good; flipping tags. ... $ lxc launch ubuntu:mantic netdata-mantic $ lxc exec netdata-mantic -- su - ubuntu

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

Steps with test packages on Focal (shutdown-on-init) --- Environment: --- On top of LXD VM in comments #12/#13. Enable PPA & debug symbols sudo add-apt-repository -yn ppa:mfo/lp2059272 sudo sed '/^deb / s,$, main/debug,' -i

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

Steps with test packages on Focal (shutdown-on-runtime) --- Environment: --- On top of LXD VM in comments #12/#13. Enable PPA & debug symbols sudo add-apt-repository -yn ppa:mfo/lp2059272 sudo sed '/^deb / s,$, main/debug,' -i

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

Steps to reproduce on Focal (shutdown-on-init) --- LXD virtual machine lxc exec lp2059272-focal -- su - ubuntu lxc exec lp2059272-focal -- su - ubuntu Latest Packages and Debug Symbols: cat

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

Steps to reproduce on Focal (shutdown-on-runtime) --- LXD virtual machine lxc exec lp2059272-focal -- su - ubuntu lxc exec lp2059272-focal -- su - ubuntu Latest Packages and Debug Symbols: cat

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

Verification done on jammy-proposed. --- Part 1: comment #2, libvirt starts without errors, and can list and manage the domain. Part 2: comment #5, libvirt restarts without errors 100 times with 10 domains. Environment: --- LXD container lxc launch --vm ubuntu:jammy lp2059272-jammy

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

** Description changed: [ Impact ]  * If a race condition occurs on libvirtd shutdown,    a QEMU domain status XML (/run/libvirt/qemu/*.xml)    might lose the QEMU-driver specific information,    such as ''.  * On the next libvirtd startup, the parsing of that    QEMU domain's

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

> Please include the "normal" execution from comment #5 in the test plan, besides the synthetic one. Done; thanks! ** Description changed: [ Impact ]  * If a race condition occurs on libvirtd shutdown,    a QEMU domain status XML (/run/libvirt/qemu/*.xml)    might lose the

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

Uploaded to Jammy. ** Description changed: [ Impact ] - * If a race condition occurs on libvirtd shutdown, -a QEMU domain status XML (/run/libvirt/qemu/*.xml) -might lose the QEMU-driver specific information, -such as ''. - - * On the next libvirtd startup, the parsing of

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

directory 106 version: 8.0.0, package: 1ubuntu7.9 (Mauricio Faria de Oliveira Wed, 27 Mar 2024 12:47:46 -0300) 1 version: 8.0.0, package: 1ubuntu7.8 (Lena Voytek Wed, 29 Nov 2023 14:52:52 -0700) -- You received this bug notification because you are a member of Ubuntu Bugs, which is su

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

Steps with test packages on Jammy --- Test packages built successfully in all architectures with -proposed enabled in Launchpad PPA mfo/lp2059272. https://launchpad.net/~mfo/+archive/ubuntu/lp2059272 Upgrade the libvirt packages and install debug symbols $ sudo add-apt-repository -y -c

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

** Description changed: + [ Impact ] + + * If a race condition occurs on libvirtd shutdown, +a QEMU domain status XML (/run/libvirt/qemu/*.xml) +might lose the QEMU-driver specific information, +such as ''. + + * On the next libvirtd startup, the parsing of that +QEMU

[Bug 2059272] Re: libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

Steps to reproduce on Jammy --- Stop libvirt systemd units sudo systemctl stop 'libvirtd*' Start libvirt in GDB sudo gdb \ -iex 'set confirm off' \ -iex 'set pagination off' \ -iex 'set debuginfod enabled on' \ -iex 'set debuginfod urls

[Bug 2059272] [NEW] libvirt domain is not listed/managed after libvirt restart with messages "internal error: no monitor path" and "Failed to load config for domain"

** Affects: libvirt (Ubuntu Focal) Importance: Medium Assignee: Mauricio Faria de Oliveira (mfo) Status: Confirmed ** Affects: libvirt (Ubuntu Jammy) Importance: Medium Assignee: Mauricio Faria de Oliveira (mfo) Status: Confirmed ** Also affects: libvirt (Ubuntu

  1   2   3   4   5   6   7   8   9   10   >