Project

General

Profile

Actions
Copy link

coordination #49157

closed

[epic] Introduce yast2_clone to more scenarios

Added by riafarov almost 6 years ago. Updated about 1 year ago.

Status:
Rejected
Priority:
Normal
Assignee:
JERiveraMoya
Target version:
QA (public) - future
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 open — 1 closed)

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

Actions
Actions
Copy link
 #1

Updated by riafarov almost 6 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by okurz almost 6 years ago

  • 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.

Actions
Copy link
 #3

Updated by riafarov over 5 years ago

  • Target version changed from Milestone 24 to Milestone 25
Actions
Copy link
 #4

Updated by JERiveraMoya over 5 years ago

  • Due date changed from 2019-05-07 to 2019-05-21

due to changes in a related task

Actions
Copy link
 #5

Updated by JERiveraMoya over 5 years ago

  • Due date changed from 2019-05-21 to 2019-06-04

due to changes in a related task

Actions
Copy link
 #6

Updated by riafarov over 5 years ago

  • Due date changed from 2019-06-04 to 2019-07-09

due to changes in a related task

Actions
Copy link
 #7

Updated by riafarov over 5 years ago

  • Target version changed from Milestone 25 to Milestone 27
Actions
Copy link
 #8

Updated by riafarov over 5 years ago

  • Due date changed from 2019-07-09 to 2020-01-14

due to changes in a related task

Actions
Copy link
 #9

Updated by mgriessmeier over 5 years ago

  • Target version changed from Milestone 27 to Milestone 28
Actions
Copy link
 #10

Updated by riafarov about 5 years ago

  • Target version changed from Milestone 28 to future
Actions
Copy link
 #11

Updated by riafarov almost 5 years ago

  • Due date changed from 2020-01-14 to 2020-01-28

due to changes in a related task

Actions
Copy link
 #12

Updated by szarate over 4 years ago

  • Tracker changed from action to coordination
Actions
Copy link
 #14

Updated by riafarov about 4 years ago

  • 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
Actions
Copy link
 #15

Updated by riafarov over 3 years ago

  • Assignee changed from riafarov to oorlov
Actions
Copy link
 #16

Updated by oorlov almost 3 years ago

  • Assignee changed from oorlov to JERiveraMoya
Actions
Copy link
 #17

Updated by JERiveraMoya about 1 year ago

  • Status changed from New to Rejected

Enough test coverage in YaST job group.

Actions
Copy link

Also available in: Atom PDF