Project

General

Profile

Actions

action #155911

closed

coordination #152769: [epic] Reduction of yaml files in YaST installations

Reduce yaml files for guided_xfs

Added by JERiveraMoya 5 months ago. Updated 6 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
2024-01-04
Due date:
% Done:

0%

Estimated time:

Description

Motivation

See epic and tickets in the epic for best practices.

Some general summary as a hint (after reading previous tickets):
Main goals are to reduce for single test suite to single yaml file comparing the ones created per each architecture before and drive the schedule having different yaml default files per each architecture. The final yaml should be stored in a folder where we have the representation of each test case: schedule/yam/test_cases
In order to do that you have to consider if it is just about yaml or would require some code changes to make things more homogeneous, there are multiple approaches ranging from simple dropping small tested functionality in some specific architecture to some more fancy code strategy.
At the same time we should care of variables, basically moving all of them to job group yaml.
Leave out for now ppc64le, due to most of our test coverage is in PowerVM and it is not working, so verification are not possible atm. Anyway in the future most likely we will have to reduce hugely test coverage for ppc64le, so we should take that into account instead of trying to do much effort in the code due to PowerVM requires special treatment in the console or installation that only make sense to have them in textmode breaking this homogeneity that we are aiming to.

Specific from this test suite:
[1] Regarding validate_partition_table_via* should be solved in #155908

[2] Understand how we could run this for s390x zVM.

- console/validate_free_space
- console/validate_read_write

Schedules for this test suite exists in schedule/yast/sle/guided_xfs.

Acceptance criteria

AC1: Reduce yaml files for corresponding test suite over all the architectures.
AC2: Apply additional refactor/investigation to those 2 modules mentioned above and make them data-driven if possible.
AC3: Clean-up unused files.

Actions #1

Updated by JERiveraMoya 4 months ago

  • Tags changed from qe-yam-mar-sprint to qe-yam-apr-sprint
Actions #2

Updated by JERiveraMoya 3 months ago

  • Tags changed from qe-yam-apr-sprint to qe-yam-may-sprint
Actions #3

Updated by JERiveraMoya 3 months ago

  • Priority changed from Normal to Low
Actions #4

Updated by JERiveraMoya about 2 months ago

  • Priority changed from Low to Normal
Actions #5

Updated by zoecao about 2 months ago

  • Status changed from Workable to In Progress
  • Assignee set to zoecao
Actions #6

Updated by JERiveraMoya about 2 months ago

  • Tags changed from qe-yam-may-sprint to qe-yam-jan-sprint
Actions #7

Updated by JERiveraMoya about 2 months ago

  • Tags changed from qe-yam-jan-sprint to qe-yam-jun-sprint
Actions #8

Updated by JERiveraMoya about 2 months ago

sorry, probably the tickets got ordered differently, you have a dependency with https://progress.opensuse.org/issues/155908
you should start by that one.

Actions #9

Updated by zoecao about 2 months ago

JERiveraMoya wrote in #note-8:

sorry, probably the tickets got ordered differently, you have a dependency with https://progress.opensuse.org/issues/155908
you should start by that one.

Thank you for your remind, I take the poo#155908 and will start with it.

Actions #10

Updated by zoecao about 1 month ago

I'll work on poo#155908 first. This ticket has dependency with poo#155908.

Actions #11

Updated by JERiveraMoya about 1 month ago

  • Status changed from In Progress to Workable

I will put in workable to be a bit more precise about what we are really working on, but still assign to you.

Actions #12

Updated by JERiveraMoya 26 days ago

  • Tags changed from qe-yam-jun-sprint to qe-yam-jul-sprint
Actions #13

Updated by zoecao 25 days ago

  • Status changed from Workable to In Progress
Actions #14

Updated by JERiveraMoya 25 days ago

If applies, please unify also ppc64le for powerVM as part of this ticket.
According to #161189 is now possible.

Actions #15

Updated by zoecao 25 days ago

OK! Include the ppc64le also. Running the VRs for all arches, will adjust the differences based on the results.
https://openqa.suse.de/tests/overview?version=15-SP6&build=chcao_1&distri=sle

Actions #16

Updated by JERiveraMoya 20 days ago

zoecao wrote in #note-15:

OK! Include the ppc64le also. Running the VRs for all arches, will adjust the differences based on the results.
https://openqa.suse.de/tests/overview?version=15-SP6&build=chcao_1&distri=sle

Regarding the failures, not sure if it will help in this case, but many test suite have a set of test module always running after first boot to avoid random failures (we call them preparation).

Actions #18

Updated by zoecao 16 days ago

Developer is helping to take a look at the issue of no output when doing blkid /dev/dasda on s390x zvm.

Actions #19

Updated by zoecao 9 days ago

Developer already helped to check it, the /dev/dasda doesn't have uuid, and can not add one manually, maybe because its host's dasda doesn't have it.
And updated the PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/19634
The latest VRs are pass: https://openqa.suse.de/tests/overview?distri=sle&build=chcao_1&version=15-SP6

Actions #20

Updated by zoecao 6 days ago

  • Status changed from In Progress to Resolved

Resolve here, thanks.

Actions

Also available in: Atom PDF