Project

General

Profile

Actions

action #156481

closed

cron -> (fetch_openqa_bugs)> /tmp/fetch_openqa_bugs_osd.log failed / No route to host / openqa.suse.de

Added by livdywan 4 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
2023-07-18
Due date:
% Done:

0%

Estimated time:

Description

Observation

Cron root@openqa-service (date; fetch_openqa_bugs)> /tmp/fetch_openqa_bugs_osd.log:

openqa_client.exceptions.ConnectionError: HTTPSConnectionPool(host='openqa.suse.de', port=443): Max retries exceeded with url: /api/v1/bugs?refreshable=1&delta=86400 (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f91f6877080>: Failed to establish a new connection: [Errno 113] No route to host',))

Suggestions


Related issues 1 (0 open1 closed)

Related to openQA Infrastructure - action #156460: Potential FS corruption on osd due to 2 VMs accessing the same diskResolvednicksinger2024-03-01

Actions
Actions #1

Updated by livdywan 4 months ago

There is also the failing scripts-ci pipeline, which seems like it might be related as it's also failing to reach osd:

++ openqa-cli api --host http://openqa.suse.de jobs version=15-SP5 scope=relevant arch=x86_64 flavor=Server-DVD-Updates test=ovs-client latest=1
++ jq -r '.jobs | map(select(.result == "passed")) | max_by(.settings.BUILD) .settings.HDD_1'
Connection refused
jq: parse error: Invalid numeric literal at line 1, column 8
+ openqa-cli schedule --monitor --host http://openqa.suse.de --param-file SCENARIO_DEFINITIONS_YAML=/tmp/tmp.lOAqHYAXDt DISTRI=sle VERSION=15-SP5 FLAVOR=Server-DVD-Updates ARCH=x86_64 BUILD=2024-03-01T14:12+00:00 _GROUP_ID=0 HDD_1=
Inactivity timeout
Request failed, hit error 0, retrying up to 60 more times after waiting …
[...]
Request failed, hit error 0, retrying up to 1 more times after waiting …
Actions #2

Updated by livdywan 4 months ago

  • Related to action #156460: Potential FS corruption on osd due to 2 VMs accessing the same disk added
Actions #3

Updated by livdywan 4 months ago

  • Status changed from New to Resolved
  • Priority changed from Urgent to Normal

I guess we're good. Since I was not actively looking at the web UI and the Slack thread was not very visible I just missed the worst of it.

Actions #4

Updated by okurz 3 months ago

  • Assignee set to livdywan
Actions

Also available in: Atom PDF