coordination #40469
closed
[functional][y][epic] Adjust RAID/LVM/partitioning tests to the new changes and extend testing coverage
Added by riafarov about 6 years ago.
Updated almost 4 years ago.
Estimated time:
(Total: 26.00 h)
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¶
- Existing tests are adjusted to the changes for distributions with storgae-ng (Leap/SLE 15, TW)
- Tickets for new tests are added as subtickets to the epic as per request from YaST team
- Target version set to Milestone 24
- Due date set to 2018-10-09
due to changes in a related task
- Due date changed from 2018-10-09 to 2018-09-19
due to changes in a related task
- 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
- Due date set to 2018-10-23
due to changes in a related task
- Due date changed from 2018-11-20 to 2018-12-04
due to changes in a related task
- Due date changed from 2018-12-04 to 2019-01-29
due to changes in a related task
- Due date changed from 2019-01-29 to 2019-02-12
due to changes in a related task
- Due date changed from 2019-02-12 to 2018-12-04
due to changes in a related task
- Due date changed from 2018-12-04 to 2019-03-12
due to changes in a related task
- Status changed from New to Blocked
- Assignee set to okurz
- Due date changed from 2019-03-12 to 2019-03-26
due to changes in a related task
- Due date changed from 2019-03-26 to 2019-12-31
due to changes in a related task
- Target version changed from Milestone 24 to Milestone 26
- 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.
- 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.
- Target version changed from Milestone 27 to Milestone 28
- Target version changed from Milestone 28 to Milestone 30+
- Due date changed from 2019-12-31 to 2020-01-28
due to changes in a related task
- Target version changed from Milestone 30+ to Milestone 30
bulk moved to M30 for revisiting
- Due date changed from 2020-01-28 to 2020-02-11
due to changes in a related task
- Due date changed from 2020-02-11 to 2020-02-25
due to changes in a related task
- Due date changed from 2020-02-25 to 2020-03-10
due to changes in a related task
- Due date changed from 2020-03-10 to 2020-03-24
due to changes in a related task
- Due date changed from 2020-03-24 to 2020-04-07
due to changes in a related task
- Due date changed from 2020-04-07 to 2020-04-21
due to changes in a related task
- Due date changed from 2020-04-21 to 2020-05-05
due to changes in a related task
- Due date changed from 2020-05-05 to 2020-01-14
due to changes in a related task: #41948
- Due date changed from 2020-01-14 to 2020-08-04
due to changes in a related task: #41948
- Status changed from In Progress to Blocked
- Target version changed from Milestone 30 to future
- Due date changed from 2020-08-04 to 2020-08-25
due to changes in a related task: #41948
- Due date changed from 2020-08-25 to 2020-09-08
due to changes in a related task: #41948
- Due date changed from 2020-09-08 to 2020-10-06
due to changes in a related task: #41948
- Status changed from Blocked to Workable
- Status changed from Workable to Resolved
- Tracker changed from action to coordination
Also available in: Atom
PDF