Project

General

Profile

Actions

action #42410

closed

openQA worker broken after a fresh install on openSUSE Tumbleweed for AArch64

Added by ggardet_arm over 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Regressions/Crashes
Target version:
-
Start date:
2018-10-12
Due date:
% Done:

0%

Estimated time:

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.


Related issues 1 (0 open1 closed)

Related to openQA Tests - action #52556: [functional][u] openqa_bootstrap on aarch64Rejectedokurz2019-06-04

Actions
Actions #1

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

Actions #2

Updated by ggardet_arm over 5 years ago

This is an EFI job for aarch64.

Actions #3

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.

Actions #4

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.

Actions #5

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
Actions #6

Updated by okurz almost 5 years ago

@ggardet_arm is this still an issue?

Actions #7

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? ;)

Actions #8

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

Actions #9

Updated by okurz almost 5 years ago

  • Related to action #52556: [functional][u] openqa_bootstrap on aarch64 added
Actions

Also available in: Atom PDF