action #120055
closed[qe-core] test fails in installation - Error while fetching the profile
0%
Description
Observation¶
openQA test in scenario sle-15-Server-DVD-Updates-s390x-Build20221107-1-qam-gnome@s390x-kvm-sle12 fails in
installation
Test suite description¶
Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml.
Reproducible¶
Fails since (at least) Build 20221107-1 (current job)
Expected result¶
Last good: 20221106-1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by dvenkatachala over 1 year ago
- Tags set to bugbusters
- Category set to Bugs in existing tests
- Target version set to QE-Core: Ready
Updated by dvenkatachala over 1 year ago
Same issue observed in other architecture and versions as well.
Updated by dvenkatachala over 1 year ago
- Subject changed from [qe-core] test fail in installation - Error while fetching the profile to [qe-core] test fails in installation - Error while fetching the profile
Updated by rfan1 over 1 year ago
- Assignee set to rfan1
WORKER_HOSTNAME : worker2 [who know this worker?]
Updated by rfan1 over 1 year ago
- Status changed from New to Resolved
The issue is caused by https://suse.slack.com/archives/C02CANHLANP/p1667830065855669?thread_ts=1667580491.234429&cid=C02CANHLANP
As Oliver mentioned, it has be fixed. so close it for now.
But we may need pay some attention for the new failure, it might be a new product bug.
https://openqa.suse.de/tests/9899717#step/installation/29
Updated by okurz over 1 year ago
https://openqa.suse.de/tests/9899476#step/installation/26 still fails and I don't see what the error is
Updated by rfan1 over 1 year ago
okurz wrote:
https://openqa.suse.de/tests/9899476#step/installation/26 still fails and I don't see what the error is
Seems vm failed to boot up in gnome mode, but succeed with texmode https://openqa.suse.de/tests/9897822
We will file another ticket [or a product bug] to track the new failure.
Updated by dvenkatachala over 1 year ago
- Related to action #120091: [qe-core] installation test is failed in s390x added
Updated by rfan1 over 1 year ago
- Status changed from Resolved to In Progress
The issue happens again https://openqa.suse.de/tests/9904691
Can you please help double check?
Updated by okurz over 1 year ago
https://openqa.suse.de/tests/9904691#step/installation/5 shows that the machine tries to access "worker2" instead of the FQDN. The worker config on worker2 says worker2.oqa.suse.de so the FQDN which should work. More recent tests like https://openqa.suse.de/tests/9905777/file/vars.json show the correct entry WORKER_HOSTNAME. I don't understand why the worker hostname was reverting to the old.
I triggered
openqa-clone-job --within-instance https://openqa.suse.de/tests/9906550 _GROUP=0 WORKER_CLASS=worker2 BUILD= TEST=qam-gnome-okurz-poo120055-crosscheck-worker_hostname
Created job #9907305: sle-15-Server-DVD-Updates-s390x-Build20221108-1-qam-gnome@s390x-kvm-sle12 -> https://openqa.suse.de/t9907305
to crosscheck.
EDIT: That failed even earlier in https://openqa.suse.de/tests/9907305#step/bootloader_start/3. Sorry, I can't help you further right now.
Updated by rfan1 over 1 year ago
- Status changed from In Progress to Resolved
With Tool team's kindly help, the issue is gone.