action #152755
closed[tools] test fails in scc_registration - SCC not reachable despite not running multi-machine tests? size:M
0%
Description
Observation¶
openQA test in scenario sle-15-SP4-Server-DVD-Updates-x86_64-qam-regression-installation-SLES@64bit fails in
scc_registration
Reproducible¶
Fails since (at least) Build 20231218-1
and seems like all SCC related jobs in at least the same build
https://openqa.suse.de/tests/overview?build=20231218-1&groupid=414&version=15-SP4&distri=sle
are affected
https://openqa.suse.de/tests/13109842#comments
shows 4x red so a clear reproducible infrastructure related issue.
but https://openqa.suse.de/tests/13111926#step/scc_registration/8
Expected result¶
Last good: 20231217-1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Suggestions¶
- SCC is up and running - it's not a general downtime of the service
TID for diagnosing SCC connectivity issues: https://www.suse.com/support/kb/doc/?id=000021034
TL;DR: This bad boi should return a reflection of the HTTP request (minus the post data)curl -sSL -d post=data -H "Authorization: Basic dXNlcjpwYXNzd29yZA==" -H "System-Token: testtoken" https://scc.suse.com/debug/reflect | python3 -m json.tool
Use a developer session to debug the issue live