Project

General

Profile

action #113716

[qe-core] proxy-scc is down

Added by maritawerner 2 months ago. Updated about 2 months ago.

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

0%

Estimated time:

Description

On Friday, July 15, at 10.45 the proxy-scc stopped working. A Jira SD ticket for eng infra was raised by QE: https://sd.suse.com/servicedesk/customer/portal/1/SD-92678

In the slack channel help-scc Jiri Novak and Thomas Schmidt from the SCC team discussed the technical details:
https://suse.slack.com/archives/C02AYV7UJSD/p1657792209257829

In short: the very old caasp cluster will be replaced by a Kubernetes instance.


Related issues

Related to openQA Infrastructure - action #113746: monitoring: The grafana "ping time" panel does not list all hosts size:SResolved2022-07-182022-08-09

Related to openQA Tests - action #107062: Multiple failures due to network issuesFeedback2021-09-27

History

#1 Updated by jlausuch 2 months ago

Current SLE Micro 5.3 development is blocked due to this issue.
https://openqa.suse.de/tests/overview?distri=sle-micro&version=5.3&build=19.1_9.4&groupid=329
I hope it gets fixed soon.

#2 Updated by szarate 2 months ago

  • Subject changed from proxy-scc is down to [qe-core] proxy-scc is down
  • Due date set to 2022-07-19
  • Status changed from New to Blocked
  • Assignee set to szarate
  • Priority changed from Normal to Urgent

waiting for updates from SCC

#3 Updated by okurz 2 months ago

  • Target version set to QE-Core: Ready

I assume we can set the "QE Core: Ready" target version then, "future" would be the alternative as long as QE Tools isn't the assignee

#4 Updated by okurz 2 months ago

  • Related to action #113746: monitoring: The grafana "ping time" panel does not list all hosts size:S added

#5 Updated by szarate 2 months ago

  • Related to action #107062: Multiple failures due to network issues added

#7 Updated by szarate 2 months ago

Jose Gomez from SCC:

I've pointed *.proxy.scc.suse.de & *.qa-proxy.scc.suse.de to hydra.scc.suse.de. It'll take effect when the current TTL expires (circa 8h). Meanwhile your options are: Wait for TTL to expire or run your jobs pointint hydra.scc.suse.de

#8 Updated by szarate 2 months ago

  • Status changed from Blocked to Feedback

#9 Updated by szarate 2 months ago

  • Status changed from Feedback to Resolved

This is finally resolved

#10 Updated by szarate about 2 months ago

  • Tags set to bugbusters

#11 Updated by szarate about 2 months ago

document on confluence

Also available in: Atom PDF