action #136055
closed[qe-core] test fails in bootloader_start
0%
Description
Observation¶
openQA test in scenario sle-15-SP1-Server-DVD-Incidents-Minimal-s390x-qam-minimal-full@s390x-zVM-vswitch-l3 fails in
bootloader_start
Test suite description¶
Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. minimal = base pattern, minimal (enhanced base) pattern are additional convenience paclkages
Reproducible¶
Fails since (at least) Build :30363:zypper-lifecycle-plugin
Expected result¶
Last good: :30602:shadow (or more recent)
Further details¶
Always latest result in this scenario: latest
First observation¶
looking at a working test https://openqa.suse.de/tests/12050494 seems that bootparam file is downloaded via FTP from $REPO_HOST=10.145.10.207
this failing test has REPO_HOST=10.160.0.207, need to investigate the reason and fix
Updated by amanzini about 1 year ago
forcing REPO_HOST to 10.145.10.207, the system boots https://openqa.suse.de/tests/12189442#live
$ openqa-clone-job https://openqa.suse.de/tests/12170027 --skip-chained-deps --host=openqa.suse.de REPO_HOST=10.145.10.207 TEST=amanzini BUILD=amanzini _GROUP=487 _GROUP_ID=487
Updated by amanzini about 1 year ago
trying to use DNS name for REPO_HOST
openqa-clone-job https://openqa.suse.de/tests/12170027 --skip-chained-deps --host=openqa.suse.de REPO_HOST=openqa.suse.de TEST=amanzini BUILD=amanzini _GROUP=487 _GROUP_ID=487 -> https://openqa.suse.de/tests/12203628
Updated by amanzini about 1 year ago
- Status changed from In Progress to Feedback
At the end we can always use DNS name here, but we are also exposing to risk of depending on that service (seems in the past we experienced slow response?). What do you think ?