Project

General

Profile

Actions
Copy link

action #121846

closed

openQABot - schedule:openqabot pipeline fails on GitLab size:S

Added by livdywan almost 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
jbaier_cz
Target version:
openQA Project - Ready
Start date:
Due date:
2022-12-27
% Done:

0%

Estimated time:

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

Related issues 2 (0 open — 2 closed)

Related to openQA Infrastructure - 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:MResolvedjbaier_cz2021-12-16

Actions
Related to QA - action #97955: [openqabot] Possible TypeError during execution "'NoneType' object is not subscriptable"Resolvedjbaier_cz2021-09-02

Actions
Actions
Copy link
 #1

Updated by livdywan almost 2 years ago

  • Copied from action #121225: bot-ng - synchronize pipeline fails on GitLab size:S added
Actions
Copy link
 #2

Updated by jbaier_cz almost 2 years ago

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.

Actions
Copy link
 #3

Updated by jbaier_cz almost 2 years ago

#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

Actions
Copy link
 #4

Updated by jbaier_cz almost 2 years ago

  • 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
Actions
Copy link
 #5

Updated by jbaier_cz almost 2 years ago

  • Copied from deleted (action #121225: bot-ng - synchronize pipeline fails on GitLab size:S)
Actions
Copy link
 #6

Updated by jbaier_cz almost 2 years ago

  • Related to action #97955: [openqabot] Possible TypeError during execution "'NoneType' object is not subscriptable" added
Actions
Copy link
 #7

Updated by jbaier_cz almost 2 years ago

  • Status changed from New to In Progress
  • Assignee set to jbaier_cz

It seems to me, that we can improve the situation by simply waiting a little more to allow the remote to fully start.

MR: https://gitlab.suse.de/qa-maintenance/openQABot/-/merge_requests/101

Actions
Copy link
 #8

Updated by openqa_review almost 2 years ago

  • Due date set to 2022-12-27

Setting due date based on mean cycle time of SUSE QE Tools

Actions
Copy link
 #9

Updated by livdywan almost 2 years ago

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.

Actions
Copy link
 #10

Updated by jbaier_cz almost 2 years ago

  • Status changed from In Progress to Resolved

Pipeline looks stable.

Actions
Copy link

Also available in: Atom PDF