Now that MBS is back online, I've done a bunch of flatpak builds and noticed the following:

Yesterday, the day after I had submitted https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2020-b63ed36598 to testing, https://bodhi.fedoraproject.org/composes/ showed a "Fedora 32 Flatpaks testing compose" push issue. I didn't write down the exact error, but it was something to do with bodhi-skopeo-lite failing to copy the image somewhere.

@mohanboddu must have resumed the push as the error was gone later yesterday. However, the updates did not appear when doing a 'flatpak update' from the testing remote, so something must have gone wrong in the process.

Today, I see a similar error about "Fedora 31 Flatpaks testing compose" when looking at https://bodhi.fedoraproject.org/composes/F31F/testing. This time the error message is:

/usr/bin/bodhi-skopeo-lite copy docker://candidate-registry.fedoraproject.org/gimp:master-3120200731114206.1 docker://registry.fedoraproject.org/gimp:master-3120200731114206.1 returned a non-0 exit code: 1

Can someone look at the logs and diagnose what's going wrong here, please? There must be an actual error message what's going wrong with the copy. I don't want to silently lose flatpak builds if something is going wrong with updating the registry.

(I'll note that I'll be mostly gone for two weeks, but @otaylor might be able with the flatpak side of things if needed.)