Actions

Copy link

action #120405

closed

Failed log file tests are transferred from Leap to Tumbleweed for s390x size:M

Added by AdaLovelace over 1 year ago. Updated over 1 year ago.

Status:

Resolved

Priority:

High

Assignee:

dheidler

Category:

Regressions/Crashes

Target version:

Ready

Start date:

2022-11-14

Due date:

% Done:

Estimated time:

Description

Observation¶

Thank you for fixing the test issue for openSUSE Leap on s390x.
We hve got the same issue on openSUSE Tumbleweed for s390x and with textmode now:
https://openqa.opensuse.org/tests/2876172#step/logs_from_installation_system/13

It seems, that the test issue with failed log file uploads has been transferred with the fix for openSUSE Leap. :(

Acceptance criteria¶

AC1: s390 tests do not fail uploading log files

Suggestions¶

Verify that previous fix has been deployed to all O3 workers (be aware that s390 tests run in containers)
Have a look at https://progress.opensuse.org/projects/openqav3/wiki/#o3-s390-workers for how the s390x worker setup is configured (on o3)

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by okurz over 1 year ago

Category set to Regressions/Crashes
Priority changed from Normal to High
Target version set to Ready

Actions

Copy link

Updated by AdaLovelace over 1 year ago

It seems, that there is a problem with the parallelization of running tests in openQA. Leap has got this issue also again.
2 days ago, it was possible to resolve these failed tests with rerunning tests one after the next one:
https://openqa.opensuse.org/tests/overview?distri=opensuse&version=15.5&build=327.1&groupid=50

Actions

Copy link

Updated by mkittler over 1 year ago

How was this solved before (for Leap specifically)? A little bit context wouldn't hurt. Otherwise I'm not sure I'm following what the problem is. If it is about fixing problems with tests itself then I'm wondering why it falls into the tools team backlog.

Your last comment sounds like there are there might be multiple openQA worker instances running that use the same s390x "VM" in the background. However, judging by /opt/s390x_rebel_replacement/workers.ini on openqaworker1 and the services running there I don't think there's such a conflict.

Actions

Copy link

Updated by AdaLovelace over 1 year ago

I can not link the issue to here:
https://progress.opensuse.org/issues/119713

Actions

Copy link

Updated by okurz over 1 year ago

Related to action #119713: Leap tests are failing because of failed log file uploading in multiple tests on s390x size:M added

Actions

Copy link

Updated by mkittler over 1 year ago

The fix done for that ticket is independent from the system being tested (whether it is Leap or Tumbleweed). So maybe the fix is just not deployed everywhere?

Actions

Copy link

Updated by livdywan over 1 year ago

Subject changed from Failed log file tests are transferred from Leap to Tumbleweed for s390x to Failed log file tests are transferred from Leap to Tumbleweed for s390x size:M
Description updated (diff)
Status changed from New to Workable

Actions

Copy link

Updated by AdaLovelace over 1 year ago

If the fix is not deployed anywhere, I am surprised that fistly only Leap was affected and now both. From my point of view, the whole accepted openQA code should be applied for our openQA tests at openSUSE.

Actions

Copy link