Update to xen-4.18.0 and rebuild of libvirt collectd and qemu due to soname changes.
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2023-7c0c58a874
Please login to add feedback.
This update's test gating status has been changed to 'waiting'.
myoung edited this update.
We're not seeing test results and the gating status isn't changing because greenwave is giving us a 502 response with the error "Unexpected error while fetching remote policies". I actually thought I'd made Bodhi display these errors :( Will have to see why that's not working, and why we're getting the error in the first place.
@kevin says he caused this: "I mistakenly made that build from a src.rpm... (which you can accidentally do if you are a koji admin)"
so he'll fix that bit, and I'll see if it makes sense to have greenwave be a bit more robust or at least communicate the error through to Bodhi so we don't have to go schlep through greenwave logs...
kevin edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update's test gating status has been changed to 'passed'.
This update cannot be pushed to stable. These builds libvirt-9.9.0-3.fc40, qemu-8.1.2-3.fc40 have a more recent build in koji's f40 tag.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update cannot be pushed to stable. These builds libvirt-9.9.0-3.fc40, qemu-8.1.2-3.fc40 have a more recent build in koji's f40 tag.
https://github.com/release-engineering/greenwave/issues/218 is the greenwave issue here. Kevin has fixed the build and edited the update, so we're now seeing the test results and the gating status has updated. though, er, it probably shouldn't be 'passed'...hmm. I think it got sent to 'passed' immediately due to the previous test passes from when the tests ran days ago, and hasn't yet flipped to failed because tests are failing now, probably because they've been restarted...
Oh, the tests are now failing for the same reason Bodhi is complaining - some of the builds in the update are now old and should be rebuilt again, I guess.
This update's test gating status has been changed to 'failed'.
libvirt and qemu have newer builds already in f40 tag I am removing these builds from the update.
humaton edited this update.
Removed build(s):
Karma has been reset.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
requested fresh builds of libvirt and qemu in the side tag
I'll do it.
qemu build is failing on something related to xen...
Yes, we know. I think there is an easy fix but I haven't heard back from the qemu team yet.
those things it's trying to use are defined (only) in
include/hw/xen/interface/arch-arm.h
, which is copied from Xen itself. that is (I guess) included when building on ARM, but not when building on x86. Trying to always include it inxen_arm.c
(whatever platform we're building on) just causes failures because now lots of stuff has competing definitions. Not sure how to proceed there (aside from reverting the qemu 8.2.0 commit that caused the problem...)One thing I don't understand - how did @crobinso 's original 8.2.0rc2 build work? I'm rather confused about that.
The 8.2.0.rc2 qemu builds works for xen 4.17 but not for xen 4.18 because there is a xen version condition in include/hw/xen/xen_native.h which is in my opinion broken.
myoung edited this update.
New build(s):
Karma has been reset.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update has been submitted for stable by bodhi