#131 Fedora-27-updates-20180405.0 DOOMED
Opened 5 years ago by dustymabe. Modified 5 years ago

pungi.global.log

[INFO    ] [FAIL] Ostree (variant Everything, arch x86_64) failed, but going on anyway.
[INFO    ] Runroot task failed: 26177092. See /mnt/koji/compose/updates/Fedora-27-updates-20180405.0/logs/x86_64/Everything/ostree-4/runroot.log for more details.
[INFO    ] [FAIL] Ostree (variant Everything, arch ppc64le) failed, but going on anyway.
[INFO    ] Runroot task failed: 26177095. See /mnt/koji/compose/updates/Fedora-27-updates-20180405.0/logs/ppc64le/Everything/ostree-2/runroot.log for more details.
  • Compose run failed because: - 26177093
[ERROR   ] Compose run failed: Runroot task failed: 26177093. See /mnt/koji/compose/updates/Fedora-27-updates-20180405.0/logs/x86_64/Everything/ostree-1/runroot.log for more details.

@sinnykumari do you mind looking at these failures?

It's failing for these composes with common error: No package matches 'grub2' .
Need to look now what recent changes caused this behavior.

It's failing for these composes with common error: No package matches 'grub2' .
Need to look now what recent changes caused this behavior.

Interesting. This is f27 so I figure that should be stable. Also we haven't seent the updates-testing composes failing for this same reason (i don't think). It is odd indeed.

It's failing for these composes with common error: No package matches 'grub2' .
Need to look now what recent changes caused this behavior.

Interesting. This is f27 so I figure that should be stable. Also we haven't seent the updates-testing composes failing for this same reason (i don't think). It is odd indeed.

Yeah, this looks odd to me as well

It turns out this was caused by a change in pungi: https://pagure.io/pungi/issue/890. I believe it's part of a change we were trying to implement to move the OSTREE composes to happen earlier in a pungi compose and thus use a different repo. @puiterwijk is working on reverting pungi on the builders for now. We'll discuss tomorrow to see the best way forward.

Login to comment on this ticket.

Metadata