We use jobrunner to schedule jobs which we missed e.g. during upgrade. However, today when I wanted to use jobrunner, it crashed:
jobrunner
[root@taskotron01 ~][PROD]# sudo -u fedmsg jobrunner --start 1519930847 No handlers could be found for logger "moksha.hub" 2018-03-01 19:10:01 - Jobrunner - INFO: Processing jobs from datagrepper for topic org.fedoraproject.prod.buildsys.build.state.change: page 1 of 1 Traceback (most recent call last): File "/bin/jobrunner", line 11, in <module> load_entry_point('jobtriggers==0.4.9', 'console_scripts', 'jobrunner')() File "/usr/lib/python2.7/site-packages/jobtriggers/jobrunner.py", line 112, in main datagrepper_jobs(args.start, args.end) File "/usr/lib/python2.7/site-packages/jobtriggers/jobrunner.py", line 86, in datagrepper_jobs data = trigger.process(msg) File "/usr/lib/python2.7/site-packages/jobtriggers/koji_build_msg.py", line 78, in process return self._process_docker(msg) File "/usr/lib/python2.7/site-packages/jobtriggers/koji_build_msg.py", line 45, in _process_docker item = utils.get_docker_registry_url(build_id) File "/usr/lib/python2.7/site-packages/jobtriggers/utils.py", line 71, in get_docker_registry_url archives = session.listArchives(build_id, type='image') File "/usr/lib/python2.7/site-packages/koji/__init__.py", line 2010, in __call__ return self.__func(self.__name, args, opts) File "/usr/lib/python2.7/site-packages/koji/__init__.py", line 2448, in _callMethod return self._sendCall(handler, headers, request) File "/usr/lib/python2.7/site-packages/koji/__init__.py", line 2361, in _sendCall return self._sendOneCall(handler, headers, request) File "/usr/lib/python2.7/site-packages/koji/__init__.py", line 2407, in _sendOneCall r.raise_for_status() File "/usr/lib/python2.7/site-packages/requests/models.py", line 935, in raise_for_status raise HTTPError(http_error_msg, response=self) requests.exceptions.HTTPError: 405 Client Error: Method Not Allowed for url: https://koji.fedoraproject.org/kojihub
Please figure out what's wrong and fix it, thanks.
I used jobrunner today on taskotron-prod and it worked fine. Let's assume this was a networking issue and reopen if it happens again.
Metadata Update from @kparal: - Issue close_status updated to: Invalid
Login to comment on this ticket.