Project

General

Profile

Actions
Copy link

action #136052

closed

bot-ng in gitlab CI runner + monitor.qe.nue2.suse.org unable to access smelt.suse.de, "No route to host"

Added by okurz 8 months ago. Updated 8 months ago.

Status:
Resolved
Priority:
Urgent
Assignee:
okurz
Category:
-
Target version:
openQA Project - Ready
Start date:
2023-09-19
Due date:
% Done:

0%

Estimated time:
Tags:
alert, network, migration, gitlab, infra, smelt, prg2

Description

Observation

https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs/1841132#L406

requests.exceptions.ConnectionError: HTTPSConnectionPool(host='smelt.suse.de', port=443): Max retries exceeded with url: /graphql?query=%7B+incidents%28status_Name_Iexact%3A%22active%22%2C+first%3A+100+%29+%7B+pageInfo+%7B+hasNextPage+endCursor%7D+edges+%7B+node+%7B+incidentId+%7D%7D%7D%7D (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7efd5ed3d588>: Failed to establish a new connection: [Errno 113] No route to host',))
Actions
Copy link
 #1

Updated by okurz 8 months ago

  • Status changed from New to Blocked
Actions
Copy link
 #2

Updated by okurz 8 months ago

  • Subject changed from bot-ng in gitlab CI runner unable to access smelt.suse.de, "No route to host" to bot-ng in gitlab CI runner + monitor.qe.nue2.suse.org unable to access smelt.suse.de, "No route to host"
Actions
Copy link
 #3

Updated by okurz 8 months ago

  • Status changed from Blocked to Resolved

Recent jobs show success, e.g. https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs/1849227 . Ticket can be resolved. SD ticket still open though

Actions
Copy link

Also available in: Atom PDF