Project

General

Profile

Actions

action #47900

closed

[tools][aarch64] incompletes on arm with `mkdir vm-snapshots: Structure needs cleaning at /usr/lib/os-autoinst/backend/qemu.pm line 413`

Added by riafarov about 5 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Regressions/Crashes
Target version:
-
Start date:
2019-02-14
Due date:
% Done:

0%

Estimated time:

Description

Observation

We get a lot of failures on arm with this error:
[2019-02-14T09:57:13.434 UTC] [debug] Backend process died, backend errors are reported below in the following lines:
mkdir vm-snapshots: Structure needs cleaning at /usr/lib/os-autoinst/backend/qemu.pm line 413.

We might have issues with fs there.

openQA test in scenario sle-15-SP1-Installer-DVD-aarch64-RAID1@aarch64 fails in
first_boot

Test suite description

Maintainer: slindomansilla, jrauch

Installation of RAID1 using expert partitioner.

Reproducible

Fails since (at least) Build 163.6

Expected result

Last good: 163.1 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by okurz about 5 years ago

@riafarov I think you know by now that the "tools team" does not look for the tag "[tools]" but I agree with you that they should :)

I am not sure though if we should treat this ticket as a "openQA bug" and move to the corresponding project or just keep hereā€¦

Actions #2

Updated by riafarov about 5 years ago

  • Project changed from openQA Tests to openQA Project
  • Category deleted (Bugs in existing tests)

@okurz. I know regarding the tags, so yes, wrong project. Adjusted now ;)

Actions #3

Updated by okurz about 5 years ago

  • Category set to Regressions/Crashes
Actions #4

Updated by mkittler about 5 years ago

Judging by the error message that really just looks like a file system issue. I don't think the QEMU backend can do anything better than just dying with an error message in that case. But it seems like the problem is gone now. At least the error didn't occur anymore in subsequent test runs in that scenario.

Actions #5

Updated by okurz over 4 years ago

  • Status changed from New to Resolved
  • Assignee set to okurz

I monitored the corresponding workers a lot and could not find this problem anywhere.

Actions

Also available in: Atom PDF