action #132926
openOSD cron -> (fetch_openqa_bugs)> /tmp/fetch_openqa_bugs_osd.log failed size:M
0%
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¶
- Make sure you can login, see https://gitlab.suse.de/OPS-Service/salt/-/blob/production/pillar/id/openqa-service_qe_suse_de.sls#L11 or ask dheidler/mkittler to do that for you
- Assuming "host unavailable', check how long the scripts retried
- Re-try more often?
- Wait longer between attemps?
- https://github.com/os-autoinst/openqa_bugfetcher
Updated by okurz over 1 year ago
- Tags set to alert, openqa-bugs, openqa-service
- Target version set to Ready
Updated by livdywan over 1 year 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
Updated by okurz over 1 year ago
https://gitlab.suse.de/OPS-Service/salt/-/merge_requests/3779 to allow access for all tools team members
Updated by okurz over 1 year ago
- Status changed from Workable to Blocked
- Assignee set to okurz
Updated by okurz over 1 year 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
Updated by okurz over 1 year 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.
Updated by jbaier_cz over 1 year 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.
Updated by okurz over 1 year 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?