coordination #49157
closed
[epic] Introduce yast2_clone to more scenarios
Added by riafarov almost 6 years ago.
Updated about 1 year ago.
Estimated time:
(Total: 3.00 h)
Description
Motivation¶
We run clone for all autoyast installations, but only for single scenario with installed system.
https://bugzilla.suse.com/show_bug.cgi?id=1057597 shows that we can eliminate risks of getting this part broken and extend coverage with low development efforts.
Ideally we should validate relevant sections of the profile to match our expectations and not only catch cases when it crashes.
Once we have profiles we should consider extending AY coverage using those.
We need to identify list of scenarios where to enable test module and activate it.
Another example: https://bugzilla.suse.com/show_bug.cgi?id=1126059
Some ideas:
1) lvm + RAID1
2) lvm + encryption
3) encryption without lvm (storgae-ng only)
4) zVM + DASD
5) zVM + ZFCP
6) baremetal (e.g. ipmi)
- Description updated (diff)
- Target version set to Milestone 24
As we discussed, as this is related to near-always failing autoyast tests and blocking us I think we should work on that soon, e.g. in milestone 24. I will try to find some other tickets to delay for later instead.
- Target version changed from Milestone 24 to Milestone 25
- Due date changed from 2019-05-07 to 2019-05-21
due to changes in a related task
- Due date changed from 2019-05-21 to 2019-06-04
due to changes in a related task
- Due date changed from 2019-06-04 to 2019-07-09
due to changes in a related task
- Target version changed from Milestone 25 to Milestone 27
- Due date changed from 2019-07-09 to 2020-01-14
due to changes in a related task
- Target version changed from Milestone 27 to Milestone 28
- Target version changed from Milestone 28 to future
- Due date changed from 2020-01-14 to 2020-01-28
due to changes in a related task
- Tracker changed from action to coordination
- Project changed from openQA Tests (public) to qe-yam
- Subject changed from [functional][y][epic] Introduce yast2_clone to more scenarios to [epic] Introduce yast2_clone to more scenarios
- Category deleted (
New test)
- Assignee set to riafarov
- Assignee changed from riafarov to oorlov
- Assignee changed from oorlov to JERiveraMoya
- Status changed from New to Rejected
Enough test coverage in YaST job group.
Also available in: Atom
PDF