action #56870
closed[sle][functional][y] Different modules for RAID creation ended up with different raid level in one of the arrays
0%
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-RAID0_gpt@64bit fails in
validate_raid
We have introduced differences on the level of raid of one of the arrays when we use different module to create RAID configuration, the new OOP module installation/partitioning/raid_gpt and a legacy one installation/partitioning_raid.
For example, for the same products we can see in openSUSE, https://openqa.opensuse.org/tests/1029646 vs https://openqa.opensuse.org/tests/1030913
or in SLE https://openqa.suse.de/tests/3350728#step/raid_gpt/268 vs https://openqa.suse.de/tests/3352340#step/partitioning_raid/197
This is controlled by test data, e.g. https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/test_data/yast/raid/raid0_gpt_uefi_test_data.yaml
That's where we set raid level for the swap partition.
Here is the link: https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Installer-DVD&machine=64bit&test=RAID0&version=15-SP2
Acceptance criteria¶
- Test setup is consistent for all RAID tests (swap partition uses same raid 0 level for all tests)
Reproducible¶
It does not fails because in validation_raid
all this conditions are introduced but it is very fragile in that way.
Expected result¶
Avoid that for the same product we have this problem, probably we need to enable the new RAID OOP module in all of them and remove conditions from validation_raid
.
Further details¶
Always latest result in this scenario: latest