Project

General

Profile

action #98727

Updated by rfan1 8 months ago

## Observation
From
The issue can be rarely seen on other platforms [Re-run the test, tests can fix the issue], but we can see the hdd can't be booted.
https://openqa.nue.suse.com/tests/7108821

[2021-09-14T14:19:03.826 CEST] [warn] !!! : qemu-system-aarch64: -blockdev driver=qcow2,node-name=hd0-overlay0,file=hd0-overlay0-file,cache.no-flush=on: Could
it on aarch64 platform many times, not open backing file: Image is not in qcow2 format sure if any performance issue with arm worker.

## Steps We used to reproduce

1) Publish
publish a qcow2 hdd with below case
http://openqa.nue.suse.com/tests/7103389

2) Run
image during our tests, and this image can be used for later tests,however the cases with the published hdd can't be booted up due to wrong format

3) We can hit the issue mentioned above

## Problem
For example:
I am wondering some performance problem with the backend worker http://openqa.nue.suse.com/tests/7103389#downloads

In this case, the test passed without any issue. but the qcow2 image seems not bootable
qemu-img info sle-15-SP3-aarch64-187.1-textmode@aarch64_sb.qcow2
image: sle-15-SP3-aarch64-187.1-textmode@aarch64_sb.qcow2
file format: raw
virtual size: 2.43 GiB (2607030272 bytes)
disk size: 2.43 GiB

## Suggestion
Add some code checking for image's format

## Workaround
a. re-trigger the job
b. switch to other worker with better performance

We used to publish a qcow2 hdd image during our tests, and this image can be used for later tests,however the hdd can't be booted up due to wrong format

Can someone help take a look at this issue?


Back