https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842022-06-28T07:11:55ZopenSUSE Project Management ToolQA - action #113087: [qa-tools][qem-bot] malformed data in smelt incident causes smelt sync failhttps://progress.opensuse.org/issues/113087?journal_id=5327542022-06-28T07:11:55Zokurzokurz@suse.com
<ul><li><strong>Tags</strong> set to <i>reactive work</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li><li><strong>Target version</strong> set to <i>Ready</i></li></ul><p>As a training exercise would be great if osukup only helps others to resolve the problem :)</p>
QA - action #113087: [qa-tools][qem-bot] malformed data in smelt incident causes smelt sync failhttps://progress.opensuse.org/issues/113087?journal_id=5329192022-06-29T08:12:26Zokurzokurz@suse.com
<ul></ul><p>Not sure how to reproduce. Could this be a sporadic error? When I call <code>./bot-ng.py -c metadata -t dummy smelt-sync</code> locally I don't see such errors. I see many lines like</p>
<pre><code>INFO: Getting info about incident 24742 from SMELT
INFO: Getting info about incident 24743 from SMELT
INFO: Getting info about incident 24744 from SMELT
…
INFO: Getting info about incident 24748 from SMELT
</code></pre> QA - action #113087: [qa-tools][qem-bot] malformed data in smelt incident causes smelt sync failhttps://progress.opensuse.org/issues/113087?journal_id=5331562022-07-01T08:37:28Zokurzokurz@suse.com
<ul><li><strong>Assignee</strong> set to <i>okurz</i></li><li><strong>Priority</strong> changed from <i>High</i> to <i>Urgent</i></li></ul> QA - action #113087: [qa-tools][qem-bot] malformed data in smelt incident causes smelt sync failhttps://progress.opensuse.org/issues/113087?journal_id=5331592022-07-01T08:38:10Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul><p><a href="https://github.com/openSUSE/qem-bot/pull/47" class="external">https://github.com/openSUSE/qem-bot/pull/47</a></p>
QA - action #113087: [qa-tools][qem-bot] malformed data in smelt incident causes smelt sync failhttps://progress.opensuse.org/issues/113087?journal_id=5331802022-07-01T18:13:27Zosukup
<ul></ul><p>PR#47 isn't fix for issue + it probably caused problem in repohash code by changing way of processing connection error in <code>requests.get</code> .. fixed in PR#48</p>
<p>to reproduce ... use <code>responses</code> to mock request with broken json, basically write test for this scenario first</p>
QA - action #113087: [qa-tools][qem-bot] malformed data in smelt incident causes smelt sync failhttps://progress.opensuse.org/issues/113087?journal_id=5332072022-07-02T04:28:34Zopenqa_reviewopenqa-review@suse.de
<ul><li><strong>Due date</strong> set to <i>2022-07-16</i></li></ul><p>Setting due date based on mean cycle time of SUSE QE Tools</p>
QA - action #113087: [qa-tools][qem-bot] malformed data in smelt incident causes smelt sync failhttps://progress.opensuse.org/issues/113087?journal_id=5333392022-07-04T07:12:10Zokurzokurz@suse.com
<ul><li><strong>Priority</strong> changed from <i>Urgent</i> to <i>High</i></li></ul><p>osukup wrote:</p>
<blockquote>
<p>PR#47 isn't fix for issue + it probably caused problem in repohash code by changing way of processing connection error in <code>requests.get</code> .. fixed in PR#48</p>
<p>to reproduce ... use <code>responses</code> to mock request with broken json, basically write test for this scenario first</p>
</blockquote>
<p>Yes, PR#47 was not providing a fix, only ensured error handling and retries. Thank you for providing the fix of the missing connection error exception. Not sure what you mean with your second sentence though.</p>
QA - action #113087: [qa-tools][qem-bot] malformed data in smelt incident causes smelt sync failhttps://progress.opensuse.org/issues/113087?journal_id=5337472022-07-05T10:21:55Zokurzokurz@suse.com
<ul></ul><p><a href="https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs/1041351#L9260" class="external">https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs/1041351#L9260</a> shows a recent failure. Now we have much better details:</p>
<pre><code>RROR: 503 Server Error: Service Unavailable for url: https://smelt.suse.de/graphql?query=%7Bincidents%28incidentId%3A+24853%29+%7B+edges+%7B+node+%7Bemu+project+repositories+%7B+edges+%7B+node+%7B+name+%7D+%7D+%7D+requestSet%28kind%3A+%22RR%22%29+%7B+edges+%7B+node+%7B+requestId+status+%7B+name+%7D+reviewSet+%7B+edges+%7B+node+%7B+assignedByGroup+%7B+name+%7D+status+%7B+name+%7D+%7D+%7D+%7D+%7D+%7D+%7D+packages+%7B+edges+%7B+node+%7B+name+%7D+%7D+%7D+%7D+%7D+%7D+%7D
Traceback (most recent call last):
File "/builds/qa-maintenance/bot-ng/qem-bot/openqabot/loader/smelt.py", line 32, in get_json
return requests.get(SMELT, params={"query": query}, verify=False).json()
File "/builds/qa-maintenance/bot-ng/qem-bot/openqabot/requests.py", line 18, in get
return s.get(url, **kwargs)
File "/usr/lib/python3.6/site-packages/requests/sessions.py", line 543, in get
return self.request('GET', url, **kwargs)
File "/usr/lib/python3.6/site-packages/requests/sessions.py", line 530, in request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3.6/site-packages/requests/sessions.py", line 650, in send
r = dispatch_hook('response', hooks, r, **kwargs)
File "/usr/lib/python3.6/site-packages/requests/hooks.py", line 31, in dispatch_hook
_hook_data = hook(hook_data, **kwargs)
File "/builds/qa-maintenance/bot-ng/qem-bot/openqabot/requests.py", line 12, in <lambda>
lambda response, *args, **kwargs: response.raise_for_status()
File "/usr/lib/python3.6/site-packages/requests/models.py", line 941, in raise_for_status
raise HTTPError(http_error_msg, response=self)
</code></pre>
<p>ok so if smelt is just unresponsive then we know what to do, just retry harder and more often :)</p>
QA - action #113087: [qa-tools][qem-bot] malformed data in smelt incident causes smelt sync failhttps://progress.opensuse.org/issues/113087?journal_id=5337502022-07-05T10:23:46Zokurzokurz@suse.com
<ul></ul><p><a href="https://github.com/openSUSE/qem-bot/pull/49" class="external">https://github.com/openSUSE/qem-bot/pull/49</a></p>
QA - action #113087: [qa-tools][qem-bot] malformed data in smelt incident causes smelt sync failhttps://progress.opensuse.org/issues/113087?journal_id=5337952022-07-05T13:04:47Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li></ul><p><a href="https://github.com/openSUSE/qem-bot/pull/49" class="external">https://github.com/openSUSE/qem-bot/pull/49</a> merged, monitoring over the next days</p>
QA - action #113087: [qa-tools][qem-bot] malformed data in smelt incident causes smelt sync failhttps://progress.opensuse.org/issues/113087?journal_id=5355442022-07-11T12:13:10Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> deleted (<del><i>2022-07-16</i></del>)</li><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>No more problems for now, should be good.</p>