#222 Koji build marked as failed due to miscommunication
Opened by mgrabovs. Modified

A scratch build of a pull request in rpms/satyr was marked as failed even though the corresponding Koji build is all green.

The job's logs show a failure communicating with Koji leading to the job being marked as failed. which should not happen (investigation courtesy of @bgoncalv).


The problem is while waiting for task status, the pipeline should not fail if there some some connection issue.

+ koji watch-task 63404214
Watching tasks (this may be safely interrupted)...
63404214 build (f35, fedora-ci_89c20369e1c44be381e4173743e1e93e_cdbe266d16672d192d533d36dfbff9ed1c852d2c_69549;forks:mfabik:rpms:satyr.f35.src.rpm): free
63404214 build (f35, fedora-ci_89c20369e1c44be381e4173743e1e93e_cdbe266d16672d192d533d36dfbff9ed1c852d2c_69549;forks:mfabik:rpms:satyr.f35.src.rpm): free -> open (buildvm-a32-12.iad2.fedoraproject.org)
63404237 rebuildSRPM (noarch): free
63404237 rebuildSRPM (noarch): free -> open (buildvm-s390x-23.s390.fedoraproject.org)
2021-03-09 09:09:39,844 [ERROR] koji: ServerOffline: database outage

On old pipeline there was this code to check the status:

https://github.com/CentOS-PaaS-SIG/upstream-fedora-pipeline/blob/master/config/Dockerfiles/fedoraci-runner/rpmbuild/koji_build_pr.sh#L72

Metadata