action #132668
Updated by livdywan 10 months ago
## Observation There is a JSON decoding failure from openqa_bugfetcher i.e. visible in an email like "Cron <root@openqa-service> (date; fetch_openqa_bugs) > /tmp/fetch_openqa_bugs_osd.log": ``` Traceback (most recent call last): File "/usr/bin/fetch_openqa_bugs", line 47, in <module> issue = issue_fetcher.get_issue(bugid) File "/usr/lib/python3.6/site-packages/openqa_bugfetcher/issues/__init__.py", line 88, in get_issue return self.prefix_table[prefix](self.conf, bugid) File "/usr/lib/python3.6/site-packages/openqa_bugfetcher/issues/__init__.py", line 24, in __init__ self.fetch(conf) File "/usr/lib/python3.6/site-packages/openqa_bugfetcher/issues/bugzilla_issue.py", line 31, in fetch data = req.json() File "/usr/lib/python3.6/site-packages/requests/models.py", line 898, in json return complexjson.loads(self.text, **kwargs) File "/usr/lib64/python3.6/json/__init__.py", line 354, in loads return _default_decoder.decode(s) File "/usr/lib64/python3.6/json/decoder.py", line 339, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) File "/usr/lib64/python3.6/json/decoder.py", line 357, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) ``` ## Suggestions - Imrove the error handling to show a clean error instead of misleading "JSON broken" - Confirm what HTTP error this is / likely it's not expected to yield JSON - Expose the bugzilla ticket details in the error handling - Investigate the underlying cause