Project

General

Profile

Actions

coordination #49157

closed

[epic] Introduce yast2_clone to more scenarios

Added by riafarov about 5 years ago. Updated 5 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
Target version:
Start date:
2019-03-18
Due date:
% Done:

100%

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)


Subtasks 1 (0 open1 closed)

action #49415: [functional][y] Enable test to validate generated profile to stagingResolvedybonatakis2019-03-18

Actions
Actions

Also available in: Atom PDF