[y][timeboxed:12h] Modify check in autoyast installation test
Related to https://progress.opensuse.org/issues/64325
After implementing the checkdescribed in above ticket, there was a malfunction noticed only on one local machine ( http://falafel.suse.cz/tests/875#step/installation/1 ). The above failure is the reason why the check only records failure and doesn't kill the test. It looks like the worker can't reach the uploaded autoyast profile, but the SUT can.
Recently, the same failure was noticed in production:
Here, AUTOYAST was set to the sle autoyast profile instead of the opensuse one but still that doesn't explain why the head($url) failed. The wrong profile was uploaded and should be reachable.
We should get more runs and see how often issue occurs.
- Root cause is identified for the failures described above.
- If safe, modify the check in autoyast installation in order to kill the test in case of failure.
#8 Updated by ybonatakis about 1 year ago
- Status changed from In Progress to Feedback
So the reason is on particular workers. Specifically
- openqaworker4 https://openqa.opensuse.org/admin/workers/97
- imagetester https://openqa.opensuse.org/admin/workers/41
- falafel.suse.cz :))
On those workers you can see that there is a
Premature connection close error which probably says that the connection is closed in the time of the request when the request is happening.
[2020-09-24T10:21:28.0755 CEST] [error] REST-API error (POST http://openqa1-opensuse/api/v1/jobs/1404726/status): Connection error: Premature connection close (remaining tries: 59)
No idea why as i could not make it into the system and the time have passed.
I tried to provide a patch which will repeat the request for a number of times and report the http status but it was behaving weird and due to the time limit of this ticket i will resolve it and create another for the "enhancement" of the subroutine.