Project

General

Profile

Actions

action #181055

closed

[alert] fetch_openqa_bugs runs into timeout/exception

Added by mkittler 3 days ago. Updated 1 day ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Regressions/Crashes
Start date:
2025-04-16
Due date:
% Done:

0%

Estimated time:

Description

The mail "Cron root@openqa-service (date; fetch_openqa_bugs /etc/openqa/bugfetcher_o3.conf) > /tmp/fetch_openqa_bugs_o3.log" was send to the OSD admin list on 16.04.25 12:02.

It ran into a timeout:

Exception occured while fetching gh#os-autoinst/os-autoinst-distri-opensuse#20172
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/urllib3/connection.py", line 160, in _new_conn
    (self._dns_host, self.port), self.timeout, **extra_kw
  File "/usr/lib/python3.6/site-packages/urllib3/util/connection.py", line 84, in create_connection
    raise err
  File "/usr/lib/python3.6/site-packages/urllib3/util/connection.py", line 74, in create_connection
    sock.connect(sa)
socket.timeout: timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 678, in urlopen
    chunked=chunked,
  File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 382, in _make_request
    self._validate_conn(conn)
  File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 983, in _validate_conn
    conn.connect()
  File "/usr/lib/python3.6/site-packages/urllib3/connection.py", line 309, in connect
    conn = self._new_conn()
  File "/usr/lib/python3.6/site-packages/urllib3/connection.py", line 167, in _new_conn
    % (self.host, self.timeout),
urllib3.exceptions.ConnectTimeoutError: (<urllib3.connection.HTTPSConnection object at 0x7f97e7a7d9b0>, 'Connection to api.github.com timed out. (connect timeout=60)')
…

This is something that can happen. Since the script is running periodically anyway we can probably ignore this error unless it persists for longer.

Actions #1

Updated by mkittler 3 days ago

  • Description updated (diff)
Actions #2

Updated by dheidler 1 day ago

  • Category set to Regressions/Crashes
  • Status changed from New to Resolved
  • Assignee set to dheidler

Yes - if there is only one alert and not 20 of them or there are no new alerts, we can ignore them.

Actions

Also available in: Atom PDF