action #121846
closed
openQABot - schedule:openqabot pipeline fails on GitLab size:S
Added by livdywan over 1 year ago.
Updated over 1 year ago.
Description
The the following recent failures:
ERROR: Unexpected response: {'errors': [{'message': 'query_timeout\nserver closed the connection unexpectedly\n\tThis probably means the server terminated abnormally\n\tbefore or while processing the request.\n', 'locations': [{'line': 1, 'column': 2}], 'path': ['requests']}], 'data': {'requests': None}}
ERROR:root:Something bad happended during reading MR data from SMELT/IBS: 'NoneType' object is not subscriptable
Acceptance criteria¶
- AC1: openQABot schedule:openqabot is executed successfully
Suggestions¶
- Looks superficially similar to #121225
- Copied from action #121225: bot-ng - synchronize pipeline fails on GitLab size:S added
cdywan wrote:
The the following recent failures:
That's just one job. The error is query_timeout, server closed the connection unexpectedly and upon retry also connection to server at "127.0.0.1", port 6432 failed: FATAL: pgbouncer cannot connect to server
As the consequent pipeline passed, this is most likely just a longer restart on the other side.
#121225 seems to be a completely different issue (this is not a gitlab-runner failure); if you are looking for a similar issue, you can try #105603
- Related to action #105603: openQABot pipeline failed: "ERROR:root:Something bad happended during reading MR data from SMELT/IBS: Expecting value: line 4 column 1 (char 3)" size:M added
- Copied from deleted (action #121225: bot-ng - synchronize pipeline fails on GitLab size:S)
- Related to action #97955: [openqabot] Possible TypeError during execution "'NoneType' object is not subscriptable" added
- Status changed from New to In Progress
- Assignee set to jbaier_cz
- Due date set to 2022-12-27
Setting due date based on mean cycle time of SUSE QE Tools
jbaier_cz wrote:
cdywan wrote:
That's just one job. The error is query_timeout, server closed the connection unexpectedly and upon retry also connection to server at "127.0.0.1", port 6432 failed: FATAL: pgbouncer cannot connect to server
As the consequent pipeline passed, this is most likely just a longer restart on the other side.
Ah. I copied the links mechanically. Apparently I got two separate notifications for the same job.
- Status changed from In Progress to Resolved
Also available in: Atom
PDF