Project

General

Profile

Actions

action #132926

open

OSD cron -> (fetch_openqa_bugs)> /tmp/fetch_openqa_bugs_osd.log failed size:M

Added by osukup 9 months ago. Updated 8 months ago.

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

0%

Estimated time:

Description

Observation

OSD cron -> (fetch_openqa_bugs)> /tmp/fetch_openqa_bugs_osd.log failed:

from traceback:

requests.exceptions.ConnectTimeout: HTTPSConnectionPool(host='api.github.com', port=443): Max retries exceeded with url: /repos/SUSE/ha-sap-terraform-deployments/issues/857 (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f7439e43b38>, 'Connection to api.github.com timed out. (connect timeout=10)'))

fetch_openqa_bug failed when fetch issues from GitHub

Acceptance criteria

  • AC1: It is understood why the error occurred
  • AC2: The error does not persist

Suggestions


Related issues 1 (0 open1 closed)

Related to openQA Infrastructure - action #133097: cron on OSD (date; fetch_openqa_bugs /etc/openqa/bugfetcher_o3.conf) > /tmp/fetch_openqa_bugs_o3.log failedResolveddheidler2023-07-20

Actions
Actions #1

Updated by okurz 9 months ago

  • Tags set to alert, openqa-bugs, openqa-service
  • Target version set to Ready
Actions #2

Updated by livdywan 9 months ago

  • Subject changed from OSD cron -> (fetch_openqa_bugs)> /tmp/fetch_openqa_bugs_osd.log failed to OSD cron -> (fetch_openqa_bugs)> /tmp/fetch_openqa_bugs_osd.log failed size:M
  • Description updated (diff)
  • Status changed from New to Workable
Actions #3

Updated by okurz 9 months ago

https://gitlab.suse.de/OPS-Service/salt/-/merge_requests/3779 to allow access for all tools team members

Actions #4

Updated by okurz 9 months ago

  • Status changed from Workable to Blocked
  • Assignee set to okurz
Actions #5

Updated by okurz 9 months ago

  • Related to action #133097: cron on OSD (date; fetch_openqa_bugs /etc/openqa/bugfetcher_o3.conf) > /tmp/fetch_openqa_bugs_o3.log failed added
Actions #6

Updated by okurz 9 months ago

  • Status changed from Blocked to Workable
  • Assignee deleted (okurz)

https://gitlab.suse.de/OPS-Service/salt/-/merge_requests/3779 merged. Assuming this was actually deployed already everyone from the team should be able to login into the system and continue investigation.

Actions #7

Updated by jbaier_cz 9 months ago

okurz wrote:

https://gitlab.suse.de/OPS-Service/salt/-/merge_requests/3779 merged. Assuming this was actually deployed already everyone from the team should be able to login into the system and continue investigation.

Maybe it was not yet deployed? Trying to login as user/root ends up with a password prompt.

Actions #8

Updated by okurz 9 months ago

jbaier_cz wrote:

okurz wrote:

https://gitlab.suse.de/OPS-Service/salt/-/merge_requests/3779 merged. Assuming this was actually deployed already everyone from the team should be able to login into the system and continue investigation.

Maybe it was not yet deployed? Trying to login as user/root ends up with a password prompt.

According to https://gitlab.suse.de/OPS-Service/salt/-/blob/b507e0378094acacde27e2bf0f7300a78fc63e7f/pillar/ssh_keys/groups/qa-tools.sls it should be root and your ssh key. @dheidler you should be still able to login as root over ssh. Can you check if new ssh keys were added to /root/.ssh/authorized_keys?

Actions #9

Updated by okurz 8 months ago

  • Target version changed from Ready to future
Actions

Also available in: Atom PDF