On 03/09/2017 10:32 PM, Adam Williamson wrote: > On Thu, 2017-03-09 at 21:41 -0500, Dusty Mabe wrote: >> >> On 03/09/2017 05:21 PM, Adam Williamson wrote: >>> On Thu, 2017-03-09 at 20:10 +0000, Fedora compose checker wrote: >>>> Missing expected images: >>>> >>>> Atomic qcow2 x86_64 >>>> Server dvd i386 >>>> Workstation live i386 >>>> Server boot i386 >>>> Atomic raw-xz x86_64 >>>> Workstation live x86_64 >>> >>> Atomic image builds seem to be failing in anaconda, with a blank screenshot: >>> https://koji.fedoraproject.org/koji/taskinfo?taskID=18277586 >>> https://koji.fedoraproject.org/koji/taskinfo?taskID=18277589 >> >> *note* I'm replying all - but some of my emails get rejected. > > I try to CC all the lists that *some* of the info is relevant to, but > if you're just replying about one specific bit, feel free to limit the > reply to the relevant list... > >> I'll try to look at this weekend. Let me know if anyone else is >> looking at this or already knows what the issue is. > > <dgilmore> adamw: we need patches in koji and pungi > <dgilmore> because ostree changed behaviour under us again > <dgilmore> without notification > <dgilmore> well I think it was bwrap but either way things changed > under us again yep. I'm aware of this issue. It's actually something we fixed in bodhi some time back, but since pungi and bodhi use different processes to create ostrees, we got bit by it again. We're hoping to make them both use the same process in the future. > > That was when I posted the create-ostree-repo log, though, which also > shows an error: > > https://kojipkgs.fedoraproject.org/compose/branched/Fedora-26-20170309.n.0/logs/x86_64/Atomic/ostree-2/create-ostree-repo.log > > not sure what the relationship is between that error and the > image creation failure. > Since the ostree generation fails it's possible there is no ostree to build the image from and that could explain the failure. Dusty _______________________________________________ cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
