action #56486
closedcoordination #40469: [functional][y][epic] Adjust RAID/LVM/partitioning tests to the new changes and extend testing coverage
[functional][y] improve raid tests workflow by cloning partition table
0%
Description
Description¶
Currently, all the raid tests are working this way:
- create some partitions on disk 1
- create the same exact set of partitions on the next disk.
- iterate the same exact operation for all the disks.
However, on both sle 12 and 15, there is possiblity to clone partitions:
Using this would drastically reduce the execution time of test modules, and makes more sense, the real users are more about to proceed this way.
Acceptance criteria¶
- Modify the existing test modules to use "clone this disk/partition"
Additional info:¶
Another way is covered by another ticket:
We can choose first "raid" > "add raid", choose some disks and then create partitions on top of the whole array. But this is not really recommended, and our tests are already using the good old documented way.
Updated by JRivrain about 5 years ago
- Related to action #40679: [functional][y] whole disk as part of an MD RAID added
Updated by riafarov about 5 years ago
Another point, we currently have no test for cloning functionality. As we have 4 disks, we won't lose coverage (quite the opposite) when using less steps.
Updated by JRivrain almost 5 years ago
- Related to deleted (action #40679: [functional][y] whole disk as part of an MD RAID)
Updated by JRivrain almost 5 years ago
Working: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/9211 but only tested raid0 on TW. Requires a whole lot of VRs.
Updated by JRivrain over 4 years ago
- Status changed from In Progress to Feedback
PR merged, let's wait and see if it passes properly everywhere before closing.
Updated by JERiveraMoya over 4 years ago
- Due date changed from 2019-12-31 to 2020-01-14
Shifting ticket after holiday period.
Updated by JRivrain over 4 years ago
- Status changed from Feedback to Resolved
Works fine everywhere, resolving.