action #42410
closedopenQA worker broken after a fresh install on openSUSE Tumbleweed for AArch64
0%
Description
On a local openQA instance, I get the following error:
[2018-10-12T13:57:50.0349 CEST] [error] UEFI_PFLASH_VARS handling Cannot find UEFI_PFLASH_VARS asset hdd//usr/share/qemu/aavmf-aarch64-vars.bin!
I think in locate_local_assets here https://github.com/os-autoinst/openQA/blob/master/lib/OpenQA/Worker/Engines/isotovideo.pm#L291
UEFI_PFLASH_VARS var is not found in asset dir, print a warning and finnaly is set to undef
Apparently, the problem is not seen on aarch64 worker from openqa.opensuse.org. My guess is it is because it uses caches, so the functions called may be different.
Updated by okurz over 5 years ago
- Category set to Regressions/Crashes
- Status changed from New to Feedback
- Assignee set to okurz
I learned this is actually not a bug and not a problem on non-UEFI jobs, adressed the misleading error message in https://github.com/os-autoinst/openQA/pull/1825
Updated by okurz over 5 years ago
- Status changed from Feedback to New
- Assignee deleted (
okurz) - Priority changed from Normal to High
I see, then I don't immediately know, sorry.
Updated by rpalethorpe over 5 years ago
I think the workaround is to copy or link /usr/share/qemu/aavmf-aarch64-vars.bin
to /var/lib/openqa/share/factory/hdd
and make sure UEFI_PFLASH_VARS
is just set to aavmf-aarch64-vars.bin
instead of the full path.
Apparently, the problem is not seen on aarch64 worker from openqa.opensuse.org. My guess is it is because it uses caches, so the functions called may be different.
Yes, this is more or less the root cause.
Updated by okurz over 5 years ago
- Subject changed from openQA worker broken after a fresh install on openSUSE Tumblewwed for AArch64 to openQA worker broken after a fresh install on openSUSE Tumbleweed for AArch64
Updated by ggardet_arm almost 5 years ago
okurz wrote:
@ggardet_arm is this still an issue?
I did not try since a while. Maybe better to create a testcase within o3? ;)
Updated by okurz almost 5 years ago
- Status changed from New to Resolved
- Assignee set to okurz
sure, why not. The test openqa_bootstrap on x86_64 is a good reference for aarch64 and could be used there as well. However given that this ticket states a potential solution (or workaround) let's cover that in a dedicated ticket -> #52556
Updated by okurz almost 5 years ago
- Related to action #52556: [functional][u] openqa_bootstrap on aarch64 added