action #56486

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

[functional][y] improve raid tests workflow by cloning partition table

Added by JRivrain 6 months ago. Updated about 1 month ago.

Status:ResolvedStart date:05/09/2019
Priority:NormalDue date:14/01/2020
Assignee:JRivrain% Done:

0%

Category:Enhancement to existing tests
Target version:QA - future
Difficulty:
Duration: 94

Description

Description

Currently, all the raid tests are working this way:

  • create some partitions on disk 1
  • create the same exact set of partitions on the next disk.
  • iterate the same exact operation for all the disks.

However, on both sle 12 and 15, there is possiblity to clone partitions:
sle12 sle15

Using this would drastically reduce the execution time of test modules, and makes more sense, the real users are more about to proceed this way.

Acceptance criteria

  • Modify the existing test modules to use "clone this disk/partition"

Additional info:

Another way is covered by another ticket:
We can choose first "raid" > "add raid", choose some disks and then create partitions on top of the whole array. But this is not really recommended, and our tests are already using the good old documented way.

History

#1 Updated by JRivrain 6 months ago

  • Description updated (diff)

#2 Updated by JRivrain 6 months ago

  • Related to action #40679: [functional][y] whole disk as part of an MD RAID added

#3 Updated by riafarov 6 months ago

  • Target version set to future

#4 Updated by riafarov 6 months ago

Another point, we currently have no test for cloning functionality. As we have 4 disks, we won't lose coverage (quite the opposite) when using less steps.

#5 Updated by JRivrain 5 months ago

  • Related to deleted (action #40679: [functional][y] whole disk as part of an MD RAID)

#6 Updated by JRivrain 5 months ago

  • Description updated (diff)

#7 Updated by riafarov 2 months ago

  • Parent task deleted (#41276)

#8 Updated by riafarov 2 months ago

  • Parent task set to #40469

#9 Updated by riafarov 2 months ago

  • Due date set to 31/12/2019

#10 Updated by JRivrain 2 months ago

  • Assignee set to JRivrain

#11 Updated by JRivrain 2 months ago

  • Status changed from New to In Progress

#12 Updated by JRivrain 2 months ago

Working: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/9211 but only tested raid0 on TW. Requires a whole lot of VRs.

#13 Updated by JRivrain about 1 month ago

  • Status changed from In Progress to Feedback

PR merged, let's wait and see if it passes properly everywhere before closing.

#14 Updated by JERiveraMoya about 1 month ago

  • Due date changed from 31/12/2019 to 14/01/2020

Shifting ticket after holiday period.

#15 Updated by JRivrain about 1 month ago

  • Status changed from Feedback to Resolved

Works fine everywhere, resolving.

Also available in: Atom PDF