action #88355


test fails in installation - split autoinst.xml for Leap only

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

Target version:
Start date:
Due date:
% Done:


Estimated time:



openQA test in scenario opensuse-15.3-DVD-x86_64-autoyast_gnome@64bit fails in

Test suite description

Testing autoyast installation with given profile and expect SLES with gnome. Please, see the profile for more details. Profile is available in distri git repo under data subdirectory. Same as autoyast_gnome but with product defined in the profile. Maintainers: riafarov, okurz

openSUSE Leap's product name is changed to Leap, it was openSUSE before, thus we need a split autoyast.xml for Leap only.
We can either expand variable, like we do for SCC_REGCODE and other variables. Or maintain 2 profiles.


Fails since (at least) Build 4.2

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by riafarov over 3 years ago

  • Project changed from openQA Tests to qe-yam
  • Category deleted (Bugs in existing tests)
  • Target version set to SLE 15 SP3
Actions #2

Updated by riafarov over 3 years ago

  • Description updated (diff)
  • Status changed from New to Workable
Actions #3

Updated by riafarov over 3 years ago

MAJOR UPDATE: this is an issue with all autoyast installations, see

So we should address all of it with the same solution.

Actions #4

Updated by riafarov over 3 years ago

  • Status changed from Workable to In Progress
  • Assignee set to riafarov
Actions #5

Updated by riafarov over 3 years ago

I've checked and there are 2 points. First, TW works well without product being defined, which is not the case for leap. Also, there is a bug on leap when product is defined.
Considering these points, and the fact that we only run 3 AY profiles, I believe that having a separate profiles is a good solution, which will also give us further flexibility in case there are more differences to TW.

Actions #6

Updated by riafarov over 3 years ago

  • Status changed from In Progress to Feedback

As of now all of the installations fail with
Let's see if that gets fixed, we can merge the PR to be prepared and revert in case expectations will be different.

Actions #8

Updated by okurz about 3 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: autoyast_gnome@uefi-2G

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed

Also available in: Atom PDF