Project

General

Profile

Actions

coordination #40469

closed

[functional][y][epic] Adjust RAID/LVM/partitioning tests to the new changes and extend testing coverage

Added by riafarov over 5 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
New test
Target version:
Start date:
2018-09-06
Due date:
2020-01-14
% Done:

100%

Estimated time:
(Total: 26.00 h)
Difficulty:

Description

Description (copied from trello)

Storage-ng has brought some very desired features that are still not available for the users because the new partitioner just clones the old UI. In addition, new features has been requested for SLE-15-SP1 that would need accommodation in the Partitioner UI.

We should find a way to accommodate the following features, since we want them in SP1:

(1) Allow full disks (no partition table) to be added as members of a software MD RAID
(1 bis) Allow full disks (no partition table) to be used as PVs of an LVM
(2) Set a device as a bcache for another one (see FATE #325346: YaST2: disk module to support caching)
(3) Allow to format a full disk (no partition table) and/or define a mount point for it (just as we do with partitions or LVs)
(3 bis) Allow to create partitions within a software MD RAID device

See https://trello.com/c/a3IdRLos/209-13-research-ui-find-a-way-to-include-all-the-new-features-in-the-partitioner

Acceptance criteria

  1. Existing tests are adjusted to the changes for distributions with storgae-ng (Leap/SLE 15, TW)
  2. Tickets for new tests are added as subtickets to the epic as per request from YaST team

Subtasks 9 (0 open9 closed)

action #40676: [functional][y] Adapt to the new workflow of "Create New Partition Table"Resolvedmloviska2018-09-06

Actions
action #40682: [functional][y] full disk as LVM PVResolvedJERiveraMoya2018-09-062019-06-18

Actions
action #41276: [functionality][y][research] Test partitions on an MD RAIDResolvedJRivrain2018-09-06

Actions
action #41876: [sle][functional][y][feature:dev:done][timeboxed:8h] jsc#SLE-3170 fate#325346 YaST2: disk module to support caching / Add bcache through the PartitionerResolvedriafarov2018-10-012019-04-09

Actions
action #41945: [functional][y] Adapt the test to the new UI of the partitionerResolvedriafarov2018-10-032018-11-20

Actions
action #42605: [functional][y][autoyast][storage-ng] Test disk directly as PVResolvedriafarov2018-10-172018-12-04

Actions
action #42731: [sle][functional][autoyast][y] AutoYaST: directly formatted disk or disk as MD memberResolvedoorlov2018-10-192019-07-30

Actions
action #43334: [functional][y] test fails to create new partition table on TWResolvedriafarov2018-11-052018-11-20

Actions
action #56486: [functional][y] improve raid tests workflow by cloning partition tableResolvedJRivrain2019-09-052020-01-14

Actions
Actions #1

Updated by okurz over 5 years ago

  • Target version set to Milestone 24
Actions #2

Updated by riafarov over 5 years ago

  • Due date set to 2018-10-09

due to changes in a related task

Actions #3

Updated by okurz over 5 years ago

  • Due date changed from 2018-10-09 to 2018-09-19

due to changes in a related task

Actions #4

Updated by okurz over 5 years ago

  • Subject changed from [functional][y][epic] Adjust RAID tests to the new changes and extend testing coverage to [functional][y][epic] Adjust RAID/LVM/partitioning tests to the new changes and extend testing coverage
Actions #5

Updated by okurz over 5 years ago

  • Due date set to 2018-10-23

due to changes in a related task

Actions #6

Updated by riafarov over 5 years ago

  • Due date changed from 2018-11-20 to 2018-12-04

due to changes in a related task

Actions #7

Updated by okurz over 5 years ago

  • Due date changed from 2018-12-04 to 2019-01-29

due to changes in a related task

Actions #8

Updated by riafarov about 5 years ago

  • Due date changed from 2019-01-29 to 2019-02-12

due to changes in a related task

Actions #9

Updated by okurz about 5 years ago

  • Due date changed from 2019-02-12 to 2018-12-04

due to changes in a related task

Actions #10

Updated by okurz about 5 years ago

  • Due date changed from 2018-12-04 to 2019-03-12

due to changes in a related task

Actions #11

Updated by okurz about 5 years ago

  • Status changed from New to Blocked
  • Assignee set to okurz

tracking subtasks

Actions #12

Updated by riafarov about 5 years ago

  • Due date changed from 2019-03-12 to 2019-03-26

due to changes in a related task

Actions #13

Updated by okurz almost 5 years ago

  • Due date changed from 2019-03-26 to 2019-12-31

due to changes in a related task

Actions #14

Updated by okurz almost 5 years ago

  • Target version changed from Milestone 24 to Milestone 26

-> subtasks

Actions #15

Updated by okurz almost 5 years ago

  • Assignee changed from okurz to riafarov

Move to new QSF-y PO after I moved to the "tools"-team. I mainly checked the subject line so in individual instances you might not agree to take it over completely into QSF-y. Feel free to reassign to me or someone else in this case. Thanks.

Actions #16

Updated by riafarov almost 5 years ago

  • Status changed from Blocked to In Progress
  • Target version changed from Milestone 26 to Milestone 27

I stop using status blocked for epics which have sub-tickets, it's in-progress as of now.

Actions #17

Updated by mgriessmeier over 4 years ago

  • Target version changed from Milestone 27 to Milestone 28
Actions #18

Updated by riafarov over 4 years ago

  • Target version changed from Milestone 28 to Milestone 30+
Actions #19

Updated by riafarov about 4 years ago

  • Due date changed from 2019-12-31 to 2020-01-28

due to changes in a related task

Actions #20

Updated by mgriessmeier about 4 years ago

  • Target version changed from Milestone 30+ to Milestone 30

bulk moved to M30 for revisiting

Actions #21

Updated by riafarov about 4 years ago

  • Due date changed from 2020-01-28 to 2020-02-11

due to changes in a related task

Actions #22

Updated by riafarov about 4 years ago

  • Due date changed from 2020-02-11 to 2020-02-25

due to changes in a related task

Actions #23

Updated by riafarov about 4 years ago

  • Due date changed from 2020-02-25 to 2020-03-10

due to changes in a related task

Actions #24

Updated by JERiveraMoya about 4 years ago

  • Due date changed from 2020-03-10 to 2020-03-24

due to changes in a related task

Actions #25

Updated by JERiveraMoya almost 4 years ago

  • Due date changed from 2020-03-24 to 2020-04-07

due to changes in a related task

Actions #26

Updated by riafarov almost 4 years ago

  • Due date changed from 2020-04-07 to 2020-04-21

due to changes in a related task

Actions #27

Updated by JERiveraMoya almost 4 years ago

  • Due date changed from 2020-04-21 to 2020-05-05

due to changes in a related task

Actions #28

Updated by riafarov almost 4 years ago

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

due to changes in a related task: #41948

Actions #29

Updated by riafarov almost 4 years ago

  • Due date changed from 2020-01-14 to 2020-08-04

due to changes in a related task: #41948

Actions #30

Updated by riafarov almost 4 years ago

  • Status changed from In Progress to Blocked
  • Target version changed from Milestone 30 to future
Actions #31

Updated by riafarov over 3 years ago

  • Due date changed from 2020-08-04 to 2020-08-25

due to changes in a related task: #41948

Actions #32

Updated by riafarov over 3 years ago

  • Due date changed from 2020-08-25 to 2020-09-08

due to changes in a related task: #41948

Actions #33

Updated by riafarov over 3 years ago

  • Due date changed from 2020-09-08 to 2020-10-06

due to changes in a related task: #41948

Actions #34

Updated by riafarov over 3 years ago

  • Status changed from Blocked to Workable
Actions #35

Updated by riafarov over 3 years ago

  • Status changed from Workable to Resolved
Actions #36

Updated by szarate over 3 years ago

  • Tracker changed from action to coordination
Actions

Also available in: Atom PDF