pungi.global.log
[LIVE_MEDIA ] [ERROR ] [FAIL] Live media (variant Labs, arch *, subvariant Scientific_KDE) failed, but going on anyway. [LIVE_MEDIA ] [ERROR ] Live media task failed: 70346768. See /mnt/koji/compose/rawhide/Fedora-Rawhide-20210618.n.0/logs/x86_64/livemedia-Labs-Scientific_KDE.x86_64.log for more details.
Variant: Labs, subvariant: Scientific_KDE task failed. Pinging maintainers: @scitech
[LIVE_MEDIA ] [ERROR ] [FAIL] Live media (variant Labs, arch *, subvariant Design_suite) failed, but going on anyway. [LIVE_MEDIA ] [ERROR ] Live media task failed: 70346767. See /mnt/koji/compose/rawhide/Fedora-Rawhide-20210618.n.0/logs/x86_64/livemedia-Labs-Design_suite.x86_64.log for more details.
Variant: Labs, subvariant: Design_suite task failed. Pinging maintainers: @luya
[LIVE_MEDIA ] [ERROR ] [FAIL] Live media (variant Labs, arch *, subvariant Astronomy_KDE) failed, but going on anyway. [LIVE_MEDIA ] [ERROR ] Live media task failed: 70346764. See /mnt/koji/compose/rawhide/Fedora-Rawhide-20210618.n.0/logs/x86_64/livemedia-Labs-Astronomy_KDE.x86_64.log for more details.
Variant: Labs, subvariant: Astronomy_KDE task failed. Pinging maintainers: @lupinix
[LIVE_MEDIA ] [ERROR ] [FAIL] Live media (variant Labs, arch *, subvariant Jam_KDE) failed, but going on anyway. [LIVE_MEDIA ] [ERROR ] Live media task failed: 70346781. See /mnt/koji/compose/rawhide/Fedora-Rawhide-20210618.n.0/logs/x86_64/livemedia-Labs-Jam_KDE.x86_64.log for more details.
Variant: Labs, subvariant: Jam_KDE task failed. Pinging maintainers: @eeickmeyer
[LIVE_MEDIA ] [ERROR ] [FAIL] Live media (variant Spins, arch *, subvariant SoaS) failed, but going on anyway. [LIVE_MEDIA ] [ERROR ] Live media task failed: 70346796. See /mnt/koji/compose/rawhide/Fedora-Rawhide-20210618.n.0/logs/x86_64/livemedia-Spins-SoaS.x86_64.log for more details.
Variant: Spins, subvariant: SoaS task failed. Pinging maintainers: @chimosky @aperezbios
[IMAGE_BUILD ] [ERROR ] [FAIL] Image build (variant Labs, arch *, subvariant Scientific) failed, but going on anyway. [IMAGE_BUILD ] [ERROR ] ImageBuild task failed: 70346831. See /mnt/koji/compose/rawhide/Fedora-Rawhide-20210618.n.0/logs/x86_64/imagebuild-Labs-Scientific-vagrant-libvirt-vagrant-virtualbox.x86_64.log for more details.
Variant: Labs, subvariant: Scientific task failed. Pinging maintainers: @scitech
[IMAGE_BUILD ] [ERROR ] [FAIL] Image build (variant Spins, arch *, subvariant SoaS) failed, but going on anyway. [IMAGE_BUILD ] [ERROR ] ImageBuild task failed: 70346847. See /mnt/koji/compose/rawhide/Fedora-Rawhide-20210618.n.0/logs/aarch64-armhfp/imagebuild-Spins-SoaS-raw-xz.aarch64-armhfp.log for more details.
[ERROR ] Compose run failed: ImageBuild task failed: 70346853. See /mnt/koji/compose/rawhide/Fedora-Rawhide-20210618.n.0/logs/aarch64-armhfp/imagebuild-Workstation-Workstation-raw-xz.aarch64-armhfp.log for more details.
Compose Total time: 6:16:52 Compose phase INIT time: 0:00:24. Compose phase PKGSET time: 0:26:31. Compose phase WEAVER: FAILED. Compose phase BUILDINSTALL time: 1:54:25. Compose phase GATHER time: 2:09:31. Compose phase OSTREE time: 0:40:55. Compose phase OSTREE_INSTALLER time: 1:05:27. Compose phase CREATEREPO time: 0:14:35. Compose phase REPOCLOSURE time: 0:02:11. Compose phase CREATEISO time: 0:09:16. Compose phase IMAGE_BUILD: FAILED. Compose phase LIVE_MEDIA time: 1:08:52.
https://koji.fedoraproject.org/koji/taskinfo?taskID=70346853
ApplianceError: Image status is FAILED: could not create appliance through libvirt. Try running qemu directly without libvirt using this environment variable: export LIBGUESTFS_BACKEND=direct Original error from libvirt: internal error: qemu unexpectedly closed the monitor: 2021-06-18T08:59:12.793696Z qemu-system-aarch64: Failed to retrieve host CPU features [code=1 int1=-1]
Scientific_KDE:
DEBUG util.py:444: 2021-06-18 08:14:58,725: Problem 1: conflicting requests DEBUG util.py:444: 2021-06-18 08:14:58,725: - nothing provides osgi(org.objectweb.asm) needed by eclipse-pde-1:4.19-5.fc35.x86_64 DEBUG util.py:444: 2021-06-18 08:14:58,725: - nothing provides osgi(org.objectweb.asm.tree) needed by eclipse-pde-1:4.19-5.fc35.x86_64 DEBUG util.py:444: 2021-06-18 08:14:58,725: Problem 2: conflicting requests DEBUG util.py:444: 2021-06-18 08:14:58,726: - nothing provides osgi(org.apache.httpcomponents.fluent-hc) needed by eclipse-mpc-1.9.1-1.fc35.noarch DEBUG util.py:444: 2021-06-18 08:14:58,726: Problem 3: conflicting requests DEBUG util.py:444: 2021-06-18 08:14:58,726: - nothing provides osgi(org.hamcrest.core) needed by eclipse-jdt-1:4.19-5.fc35.noarch DEBUG util.py:444: 2021-06-18 08:14:58,726: Problem 4: conflicting requests DEBUG util.py:444: 2021-06-18 08:14:58,726: - package python3-spyder-4.2.5-2.fc35.noarch requires python3-pyls_black, but none of the providers can be installed DEBUG util.py:444: 2021-06-18 08:14:58,726: - nothing provides python3.10dist(python-language-server) needed by python3-pyls_black-0.4.6-3.fc35.noarch DEBUG util.py:444: 2021-06-18 08:14:58,726: Problem 5: conflicting requests DEBUG util.py:444: 2021-06-18 08:14:58,726: - package eclipse-egit-5.11.0-1.fc35.noarch requires osgi(org.eclipse.jdt.core), but none of the providers can be installed DEBUG util.py:444: 2021-06-18 08:14:58,726: - package eclipse-egit-5.11.0-1.fc35.noarch requires osgi(org.eclipse.jdt.ui), but none of the providers can be installed DEBUG util.py:444: 2021-06-18 08:14:58,727: - nothing provides osgi(org.hamcrest.core) needed by eclipse-jdt-1:4.19-5.fc35.noarch
python-language-server is fixed. No idea what to do about eclipse.
@zbyszek scientific_KDE is not a blocking image. The issue lists the failure that actually caused the compose to fail at the end, with "Compose run failed because..." Any failure before that line is a non-fatal one.
There was a new qemu build yesterday which is the obvious suspect. @crobinso , any ideas here? Key error seems to be qemu-system-aarch64: Failed to retrieve host CPU features [code=1 int1=-1], on an aarch64 image build task.
qemu-system-aarch64: Failed to retrieve host CPU features [code=1 int1=-1]
Note there's quite a lot more change in that build than the changelog lets on. It includes all of these:
@zbyszek scientific_KDE is not a blocking image.
I know. But I think it's still prudent to fix the other images ;)
Ah, there is another logical suspect too - a new kernel build. So let's tag @jforbes into the party. Justin, Rawhide compose failed today on an aarch64 image build with qemu-system-aarch64: Failed to retrieve host CPU features [code=1 int1=-1], could the new kernel version be involved? Thanks!
While yesterdays kernel build did include the most recent kvm pull, the changes brought in are entirely in 'arch/x86/kvm/' and selftests, so they would not be related to aarch64 here.
git diff --stat 39519f6a56e398544d270fcb548de99b54421d43 arch/x86/kvm/cpuid.c | 1 + arch/x86/kvm/lapic.c | 3 +++ arch/x86/kvm/mmu/mmu.c | 26 +++++++++++++++++++++++++- arch/x86/kvm/svm/avic.c | 6 +++--- arch/x86/kvm/svm/sev.c | 20 +++++++++++++++----- arch/x86/kvm/vmx/vmx.c | 1 + arch/x86/kvm/x86.c | 6 +++++- tools/testing/selftests/kvm/lib/kvm_util.c | 2 +- tools/testing/selftests/kvm/lib/test_util.c | 38 +++++++++++++++++++------------------- 9 files changed, 73 insertions(+), 30 deletions(-)
OK. There is also yet another suspect, it turns out: glibc-2.33.9000-22.fc35. The previous compose used -18, so we got all the change from -19, -20, -21 and -22:
* Thu Jun 17 2021 Florian Weimer <fweimer@redhat.com> - 2.33.9000-22 - Export libthread_db symbols under GLBIC_PRIVATE (#1965374) * Thu Jun 17 2021 Florian Weimer <fweimer@redhat.com> - 2.33.9000-21 - Redo the crafted libc.so.6 symbol table for valgrind (#1965374) * Thu Jun 17 2021 Florian Weimer <fweimer@redhat.com> - 2.33.9000-20 - Remove .symtab from libc.so.6 again (#1965374) * Thu Jun 17 2021 Florian Weimer <fweimer@redhat.com> - 2.33.9000-19 - Drop glibc-rh697421.patch: The ISO-10646-UCS-2// alias for UTF-8 is incorrect (#1972520)
I'll go see if I can find anything else critical that changed at the same time as all the others...
So, qemu shouldn't be related here... this is not in a chroot, it's using the builder qemu. Also, it looks like it did the base image, but then failed on the guestfs run that happens at the end to do things...
Not much else has changed on the builder. :(
Perhaps it's worth just refiring and confirming it fails?
Hmm. Also, it looks like most aarch64 image builds succeeded. Compared to yesterday, this Workstation failure is the only new failure. If this was a general issue caused by some change in the package set you'd sort of expect it to affect more than one image, right? Maybe this was some kind of temporary blip, or maybe it's the specific host that's got a problem? This task ran on buildhw-a64-24.iad2.fedoraproject.org . I'm not sure if you can query koji for all tasks run on a specific host...
so yeah, +1 to refire and see what happens.
Metadata Update from @humaton: - Issue status updated to: Closed (was: Open)