action #113716
closed[qe-core] proxy-scc is down
0%
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.
Updated by jlausuch over 2 years 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.
Updated by szarate over 2 years 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
Updated by okurz over 2 years 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
Updated by okurz over 2 years ago
- Related to action #113746: monitoring: The grafana "ping time" panel does not list all hosts size:S added
Updated by szarate over 2 years ago
- Related to action #107062: Multiple failures due to network issues added
Updated by szarate over 2 years 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
Updated by szarate over 2 years ago
- Status changed from Feedback to Resolved
This is finally resolved
Updated by szarate over 2 years ago
rough doc added to: https://confluence.suse.com/display/qasle/What+to+do+when+proxy-scc+is+down and https://progress.opensuse.org/issues/114917 has been also created