action #36733
closed[functional][s390x][y][medium] test fails sporadically in scc_registration
0%
Description
Observation¶
openQA test in scenario sle-15-Installer-DVD-s390x-ssh-X@s390x-zVM-vswitch-l3 fails in
scc_registration while contacting the registration server.
Already happened around a week before: https://openqa.suse.de/tests/1729269
Reproducible¶
The issue seems to be very sporadic. It is the second time I stumble across this. Restarting the job normally fixes it.
Further details¶
This issue could be related to some product-issue but we need more debug output to be sure about this.
I'd include some basic checks after the popup is shown for too long - e.g. ping the relevant servers (SCC, gateway) and/or test the name-resolution of the proxy-url.
Updated by nicksinger almost 6 years ago
- Description updated (diff)
After investigating the logs @mgriessmeier noticed that job#1729269 got a "401 Unauthorized" reply while job#1741736 "only" complained about missing authentication files. So maybe these two are not related and only show the same symptoms.
Updated by mgriessmeier almost 6 years ago
- Due date changed from 2018-06-05 to 2018-06-19
- Status changed from New to Workable
Updated by mgriessmeier almost 6 years ago
- Subject changed from [functional][s390x][fast] test fails sporadically in scc_registration to [functional][s390x][fast][y] test fails sporadically in scc_registration
Updated by riafarov almost 6 years ago
- Subject changed from [functional][s390x][fast][y] test fails sporadically in scc_registration to [functional][s390x][y] test fails sporadically in scc_registration
Updated by mgriessmeier almost 6 years ago
- Subject changed from [functional][s390x][y] test fails sporadically in scc_registration to [functional][s390x][y][medium] test fails sporadically in scc_registration
Updated by mgriessmeier almost 6 years ago
- Priority changed from Normal to High
fails again in Build 665.2
worked 3 builds in between
it's again only visible on ssh-X scenario...
so I wonder how the ssh scenario is related to scc
-> raising prio
Updated by mgriessmeier almost 6 years ago
mgriessmeier wrote:
fails again in Build 665.2
worked 3 builds in between
it's again only visible on ssh-X scenario...
so I wonder how the ssh scenario is related to scc
-> raising prio
from the logs, I can see again a 401:
HTTP response: 401 Login failed (URL: http://all-665.2.proxy.scc.suse.de/access/services/1569/repo/repoindex.xml?credentials=SUSE_Linux_Enterprise_Server_15_s390x)
However, this seems to be not related, because I can find the same output in a successful job: https://openqa.suse.de/tests/1746508
so maybe this is just a
Updated by okurz almost 6 years ago
- Target version set to Milestone 17
In any case IMHO logs should not confuse the reader with "FAILED FAILED FAILED" in the happy-path :) You already asked #happy-customer, I guess you can also ask #yast or let [y] do this
Updated by riafarov almost 6 years ago
- Status changed from Workable to In Progress
Updated by riafarov almost 6 years ago
Related bug: https://bugzilla.suse.com/show_bug.cgi?id=1072392
Updated by riafarov almost 6 years ago
- Status changed from In Progress to Feedback
PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5211
Also, we have needle for "contacting reg server", so we wait 5 seconds and repeat. In case of ssh installation, needle doesn't match. In case we want to give 250 seconds (50 iterations with 5 second sleeps), we can have proper needle.
Updated by riafarov almost 6 years ago
I guess we can resolve it as it's sporadic issue and we won't have too many runs to proceed further. But in general DoD includes run on OSD, so I've triggered this build: https://openqa.suse.de/tests/1760528#settings
Updated by okurz almost 6 years ago
Why not trigger 1k runs over the weekend for statistics and check if you can reproduce. I don't know why dheidler seems so keen on closing tickets which will just pop up again ;)
Updated by okurz almost 6 years ago
- Target version changed from Milestone 17 to Milestone 17
Updated by riafarov almost 6 years ago
@okurz: Iw as not able to reproduce this issue, but as mentioned above, I've created needle which will give more time, as it's already in the code.
Updated by riafarov almost 6 years ago
Test fails ~ every 5-th time, triggered 10 runs on OSD: https://openqa.suse.de/tests/1765723#settings and previous.
Updated by riafarov almost 6 years ago
- Status changed from Feedback to Resolved
All 10 runs worked successfully.