action #93222
closed
[qem][partitioning][maint] test fails in partitioning_raid - partitioning guide looks different in 15-SP3
Added by vsvecova almost 3 years ago.
Updated almost 2 years ago.
Category:
Bugs in existing tests
Description
Needles and possibly other adjustments need to be done.
Observation¶
openQA test in scenario sle-15-SP3-Server-DVD-Incidents-Minimal-x86_64-qam-minimal-RAID1@64bit-smp fails in
partitioning_raid
Test suite description¶
Installation of RAID1 using expert partitioner
minimal = base pattern, minimal (enhanced base) pattern are additional convenience paclkages
Reproducible¶
Fails since (at least) Build :19526:shim
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
- Status changed from New to In Progress
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to New
- Assignee set to JERiveraMoya
- % Done changed from 100 to 50
This change is only for SP3, for older version is required the original schedule file or main.pm. UI only changed drastically in SP3.
I can see here you are running it in the correct way without the libyui: https://openqa.suse.de/tests/6203314
Yes because it is not using yaml, but when you create yaml for test it should cover all versions.
dzedro wrote:
Yes because it is not using yaml, but when you create yaml for test it should cover all versions.
It cannot cover all versions if the modules that are used are different, and they are different because of the switch to libyui REST api.
yaml file also contains test data which could be changed, for example when there is duplicated information. There is not guarantee at the moment to have that expectation (technically speaking) and get the benefit of this more stable approach with the modules not containing branching (if/else etc.) We are working to have that expectation in the future making more small and meaningful steps in the tests so any product can apply the same (schedule/ business logic), but it is a long way.
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
- Status changed from New to Resolved
we will consider addding raid in some point.
Also available in: Atom
PDF