koji_utils: configure koji connection timeout to 5 minutes
ClosedPublic

Authored by kparal on Apr 10 2015, 12:17 PM.

Details

Summary

Otherwise the connection could have been waiting for up to 12 hours by
default. That's not fit for our purposes.

I'm trying to find out why this timed out:
http://taskotron-dev.fedoraproject.org/taskmaster/builders/x86_64/builds/6635/steps/runtask/logs/stdio

This is in Koji source code:

# set a default 12 hour connection timeout.
# Some Koji operations can take a long time to return, but after 12
# hours we can assume something is seriously wrong.
timeout = self.opts.setdefault('timeout',  60 * 60 * 12)

I think that a koji connection got stuck and waited for too long. I've already added some debug messages to upgradepath to help debug it next time. By configuring the timeout in koji_utils I hope we will avoid the problem completely.

Test Plan

couldn't really test this, but at least ran upgradepath manually to see if it works normally

Diff Detail

Repository
rLTRN libtaskotron
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
kparal retitled this revision from to koji_utils: configure koji timeout to 5 minutes.Apr 10 2015, 12:17 PM
kparal updated this object.
kparal edited the test plan for this revision. (Show Details)
kparal added reviewers: jskladan, mkrizek, tflink.
kparal retitled this revision from koji_utils: configure koji timeout to 5 minutes to koji_utils: configure koji connection timeout to 5 minutes.Apr 10 2015, 2:30 PM
mkrizek accepted this revision.Apr 10 2015, 3:34 PM
This revision is now accepted and ready to land.Apr 10 2015, 3:34 PM
jskladan accepted this revision.Apr 14 2015, 8:56 AM

If the timeout still triggers retry, it's good for me.

This revision was automatically updated to reflect the committed changes.