action #52418

action #40475: [functional][y][saga] Establish YaST team split

action #42854: [functional][y][epic] Introduce relevant installation validation test modules

[functional][y] Validate setup in lvm+RAID1 test suite

Added by riafarov 10 months ago. Updated 5 months ago.

Status:ResolvedStart date:31/05/2019
Priority:HighDue date:08/10/2019
Assignee:ybonatakis% Done:

0%

Category:New test
Target version:SUSE QA tests - Milestone 28
Difficulty:
Duration: 93

Description

Motivation

As of now it's more like automated installation. I as a QA engineer would like to detect if SUT gets configured as expected.

Acceptance criteria

  1. Partitioning is validated for lvm+RAID1 scenarios where enabled (SLES 12 and 15, TW)

Suggestions

Test is enabled on UEFI, xen and hyperv. So, we have slightly different expectations. Having data driven test module would be perfect fit here.

History

#1 Updated by riafarov 10 months ago

  • Subject changed from [functional][y] Introduce test module for lvm+RAID1 test to [functional][y] Validate setup in lvm+RAID1 test suite
  • Description updated (diff)
  • Estimated time set to 5.00

#2 Updated by riafarov 10 months ago

  • Status changed from New to Workable

#3 Updated by ybonatakis 9 months ago

  • Status changed from Workable to In Progress
  • Assignee set to ybonatakis

#4 Updated by riafarov 9 months ago

  • Due date changed from 09/07/2019 to 30/07/2019

#5 Updated by ybonatakis 9 months ago

  • Status changed from In Progress to Feedback

#6 Updated by riafarov 8 months ago

  • Due date changed from 30/07/2019 to 13/08/2019
  • Target version changed from Milestone 26 to Milestone 27

Review comments are addressed, needs another review + missing VRs.
For SLE 15, we can clone SP1 job, all mediums are still available.

#7 Updated by ybonatakis 8 months ago

  • Assignee deleted (ybonatakis)

still waiting for VR

#8 Updated by riafarov 8 months ago

  • Due date changed from 13/08/2019 to 27/08/2019
  • Status changed from Feedback to Workable

PR not merged and needs some adjustments.

#9 Updated by JERiveraMoya 8 months ago

  • Status changed from Workable to In Progress
  • Assignee set to JERiveraMoya

I will try to test the code creating yamls for other scenarios, solving some minor comments on the PR and applying commits on top.

#10 Updated by JERiveraMoya 7 months ago

  • Assignee deleted (JERiveraMoya)

Assigning myself, sorry, I didn't have time to take a look at the end. @ybonatakis, if you are back, you can assign back to you to continue.

#11 Updated by ybonatakis 7 months ago

  • Assignee set to ybonatakis

#12 Updated by ybonatakis 7 months ago

  • Status changed from In Progress to Feedback

#13 Updated by riafarov 7 months ago

  • Due date changed from 27/08/2019 to 10/09/2019
  • Status changed from Feedback to In Progress

#14 Updated by ybonatakis 7 months ago

  • Status changed from In Progress to Feedback

i run validations for TW and SLE12. SLE15 is broken for now. i have updated the PR and is ready for reviews.

#15 Updated by riafarov 7 months ago

  • Due date changed from 10/09/2019 to 24/09/2019
  • Estimated time deleted (5.00)

Schedules + test data might need more love.

#16 Updated by ybonatakis 7 months ago

https://bugzilla.suse.com/show_bug.cgi?id=1150370 has been filed for the difference between the RAID1 of sle12 and sle15.

#17 Updated by mgriessmeier 7 months ago

  • Target version changed from Milestone 27 to Milestone 28

#18 Updated by JERiveraMoya 6 months ago

  • Status changed from Feedback to Resolved

#19 Updated by dimstar 6 months ago

  • Status changed from Resolved to In Progress

New test fails in Tumbleweed - please investigate/correct:

https://openqa.opensuse.org/tests/1040608#step/validate_lvm_raid1/63

#20 Updated by JERiveraMoya 6 months ago

  • Due date changed from 24/09/2019 to 08/10/2019

#21 Updated by JERiveraMoya 6 months ago

  • Priority changed from Normal to High

Setting higher priority as we need to attend breaks first.

#22 Updated by ybonatakis 6 months ago

  • Status changed from In Progress to Feedback

#23 Updated by ybonatakis 6 months ago

  • Status changed from Feedback to Resolved

#24 Updated by okurz 5 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: lvm+RAID1
https://openqa.opensuse.org/tests/1063675

To prevent further reminder comments one of the following options should be followed:
1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
2. The openQA job group is moved to "Released"
3. The label in the openQA scenario is removed

Also available in: Atom PDF