pungi.global.log
[INFO ] [FAIL] Buildinstall (variant Server, arch x86_64) failed, but going on anyway. [INFO ] Runroot task failed: 28012987. See /mnt/koji/compose/rawhide/Fedora-Rawhide-20180704.n.0/logs/x86_64/buildinstall-Server.x86_64.log for more details.
[INFO ] [FAIL] Buildinstall (variant Everything, arch s390x) failed, but going on anyway. [INFO ] Runroot task failed: 28012984. See /mnt/koji/compose/rawhide/Fedora-Rawhide-20180704.n.0/logs/s390x/buildinstall-Everything.s390x.log for more details.
[INFO ] [FAIL] Buildinstall (variant Server, arch aarch64) failed, but going on anyway. [INFO ] Runroot task failed: 28012965. See /mnt/koji/compose/rawhide/Fedora-Rawhide-20180704.n.0/logs/aarch64/buildinstall-Server.aarch64.log for more details.
[INFO ] [FAIL] Buildinstall (variant Server, arch s390x) failed, but going on anyway. [INFO ] Runroot task failed: 28012985. See /mnt/koji/compose/rawhide/Fedora-Rawhide-20180704.n.0/logs/s390x/buildinstall-Server.s390x.log for more details.
[ERROR ] Compose run failed: Runroot task failed: 28012986. See /mnt/koji/compose/rawhide/Fedora-Rawhide-20180704.n.0/logs/x86_64/buildinstall-Everything.x86_64.log for more details.
So, this is failing because shim-x64, for some reason, went missing from the compose. I don't know why it went missing. The last time the compose succeeded, it had shim-x64-15-5 in it, from https://koji.fedoraproject.org/koji/buildinfo?buildID=1079378 , which is still tagged f29.
It seems the 0604.n.0 compose has shim-unsigned-0.8-1.fc22.x86_64.rpm in it, which the 0602.n.0 compose did not. That comes from this extremely old shim package build which has been tagged into every release since f22. It provides "shim-unsigned" and "shim-unsigned(x86-64)".
@pjones , any idea what's going on here?
So, @pjones tagged this into f29-pending: Tue Mar 6 17:04:48 2018: shim-0.8-1.fc22 tagged into f29-pending by pjones. Since then, it's been stuck in the signing queue (due to autopen permissions), and yesterday when I resubmitted the existing signing queue, it got tagged into f29 (because permissions got fixed). Then pungi grabs the last tagged one for the compose, so this older shim got pulled as the compose contents.
Tue Mar 6 17:04:48 2018: shim-0.8-1.fc22 tagged into f29-pending by pjones
For the record, I've untagged the shim-0.8-1.fc22 from f29.
shim-0.8-1.fc22
Metadata Update from @puiterwijk: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.