Project

General

Profile

Actions
Copy link

action #87806

closed

[s390x][Leap] 15.3 iso image can not be loaded because of a wrong file name

Added by skriesch over 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
binary_sequence
Category:
Bugs in existing tests
Target version:
-
Start date:
2021-01-15
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-15.3-DVD-s390x-textmode@s390x-zVM-vswitch-l2 fails in
bootloader_s390

The test iso image can not be loaded, because of a wrong name. The called image has got a name as openSUSE-Leap-15.3-oss-i586-x86_64-aarch6. That should be s390x specific.

Test suite description

Maintainer: okurz

Installation in textmode and selecting the textmode "desktop" during installation.

Reproducible

Fails since (at least) Build 32.4

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by skriesch over 3 years ago

It seems I don't have access to these mirrors, because they're SUSE internal. I thought, it would be possible, that I can fix this issue.

Actions
Copy link
 #2

Updated by skriesch over 3 years ago

It seems that the name is too long.

Actions
Copy link
 #3

Updated by skriesch over 3 years ago

There are 2 options:
1) The install line is cut off. Note, that in the parmfile (probably set from qaboot), each line cannot exceed 80 characters. To have a continuation, just continue in the first column of the subsequent line. Also note, that the maximum number of lines is 10.
2) Symlink to make the path shorter

Such changes can be done in https://github.com/os-autoinst/openqa-trigger-from-obs

Actions
Copy link
 #4

Updated by SLindoMansilla about 3 years ago

  • Status changed from New to In Progress
  • Assignee set to binary_sequence

Hi Sarah,

the real character limit is 72 or 73 when splitting a line in two and the real line limit is 8. (I don't know if it depends on the z/VM version or the linuxrc version)

The fix should be similar to: https://github.com/os-autoinst/openqa-trigger-from-obs/commit/89b7cc1c011252793f84028837103a66c622c08b

Actions
Copy link
 #5

Updated by skriesch about 3 years ago

Hi Sergio,

my problem is, that I am not allowed to contribute to the openQA repo openqa-trigger-from-obs at the moment. I am waiting for the legal approval since January.
I can not fix this issue without legal approval for this single repository.

Actions
Copy link
 #6

Updated by SLindoMansilla about 3 years ago

skriesch wrote:

my problem is, that I am not allowed to contribute to the openQA repo openqa-trigger-from-obs at the moment. I am waiting for the legal approval since January.
I can not fix this issue without legal approval for this single repository.

I will try to create a PR today ;)

Actions
Copy link
 #7

Updated by SLindoMansilla about 3 years ago

I am receiving help from https://github.com/andrii-suse
It is very difficult to find a solution.

Since all the arch-specific repos are under the same directory, just changing i586-x86_64-aarch64-ppc64le-s390x to ${arch} doesn't work, because there is only one directory and it doesn't populate rsync commands for non-x86_64.

The arch directory name seems to be parsed by some script to be added to openQA as setting to the job with that arch, just removing i586-x86_64-aarch64-ppc64le-s390x from the name sync the folder properly but doesn't populate the repositories to openQA job settings.

Still looking for a solution.

Actions
Copy link
 #9

Updated by SLindoMansilla about 3 years ago

  • Status changed from In Progress to Resolved

Next issue missing needles: #89464

Actions
Copy link

Also available in: Atom PDF