Project

General

Profile

Actions

action #113561

closed

failed pipelines for openQABot and bot-ng because of an expired cert

Added by tinita about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
-
Target version:
Start date:
2022-07-13
Due date:
% Done:

0%

Estimated time:

Description

https://gitlab.suse.de/qa-maintenance/openQABot/-/jobs/1053099
https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs/1053069

ERROR: Job failed (system failure): prepare environment: setting up credentials: Post "https://caasp-master.suse.de:6443/api/v1/namespaces/gitlab/secrets": x509: certificate has expired or is not yet valid: current time 2022-07-13T14:23:34Z is after 2022-07-13T13:56:25Z. Check https://docs.gitlab.com/runner/shells/index.html#shell-profile-loading for more information

Rollback steps

Disable CI in a project


Related issues 2 (0 open2 closed)

Related to openQA Infrastructure - action #68869: automatic ARM recovery jobs fail due to caasp master running gitlab CI jobs have expired certificatesResolvedokurz2020-07-12

Actions
Related to openQA Infrastructure - action #97364: openqaworker-arm-2 and openqaworker-arm-3 seem to be offline, alerts had been triggered size:SResolvednicksinger2021-08-23

Actions
Actions #1

Updated by jbaier_cz about 2 years ago

According to https://suse.slack.com/archives/C029APBKLGK/p1657723209582119, there is already SD-92579 for that issue.

Actions #2

Updated by okurz about 2 years ago

  • Status changed from New to Blocked
  • Assignee set to okurz
  • Priority changed from High to Urgent

Created our own ticket to get feedback from SUSE-IT as we can't access another one's Jira SD ticket: https://sd.suse.com/servicedesk/customer/portal/1/SD-92602

Actions #3

Updated by okurz about 2 years ago

  • Tags set to reactive work
Actions #4

Updated by livdywan about 2 years ago

  • Description updated (diff)

Because I was getting several emails a minute I switched off CI for both affected projects. See the description for rollback steps.

Actions #5

Updated by jbaier_cz about 2 years ago

  • Related to action #68869: automatic ARM recovery jobs fail due to caasp master running gitlab CI jobs have expired certificates added
Actions #6

Updated by jbaier_cz about 2 years ago

  • Related to action #97364: openqaworker-arm-2 and openqaworker-arm-3 seem to be offline, alerts had been triggered size:S added
Actions #7

Updated by okurz about 2 years ago

CI jobs are enabled and mostly look ok but some still have problems, e.g. accessing gitlab.suse.de, see https://gitlab.suse.de/qa-maintenance/openQABot/-/jobs/1053868#L21 as an example.

Actions #8

Updated by okurz about 2 years ago

  • Status changed from Blocked to Resolved

Both referenced Jira-SD tickets have been resolved, the DNS resolution problem was solved. https://gitlab.suse.de/qa-maintenance/openQABot/-/jobs and https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs looks green again.

Actions

Also available in: Atom PDF