ok the ostrees got created this time but the installers failed with error: No such branch 'fedora/29/x86_64/testing/atomic-host' in repository summary i wonder if robosig is signing it properly and updating the refs. Maybe we can have @puiterwijk look.

the imagebuild failed because of https://pagure.io/releng/issue/7703

actually I think this is another instance of https://pagure.io/robosignatory/issue/19, @nirik can you add the directories? fedora/29/{x86_64,aarch64,ppc64le}/testing

but the compose should have waited indefinitely for the ref to pop up in the repo. pungi-wait-for-signed-ostree-handler should have pretty much waited forever I think.. @lsedlar any idea why it didn't?

sigh cc @kevin ^^

actually on 2nd thought maybe we should wait to fix the directories until @lsedlar has had a chance to investigate

kevin is going to wait to create the directories (that fixes the first issue) until we can investigate why pungi-wait-for-signed-ostree-handler isn't working as expected

Well, it looks like it tried to sign it, but couldn't write it:

[2018-08-29 22:07:27][robosignatory.work INFO] Commit was succesfully signed, writing ref fedora/29/x86_64/testing/atomic-host
IOError: [Errno 2] No such file or directory: u'/mnt/fedora_koji/koji/compose/atomic/repo/refs/heads/fedora/29/x86_64/testing/atomic-host'

So, I think it signed it, but when trying to write the dirs were not there and it failed.
So IMHO making the dirs should fix it.

I think i see the problem. pungi-wait-for-signed-ostree-handler just waits for the commit object to be signed (done by robosignatory) but it does not wait for the ref to be updated to match the commit (also done by robosignatory). In our case right here the 2nd part in robosig is failing but the pungi-wait-for-signed-ostree-handler doesn't check for that.

I'll open an RFE.. @kevin, please go ahead and create the directories

Done!