Project

General

Profile

action #42941

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

action #42494: [epic][functional][y] Split/adapt scenarios to move installer related part to YaST specific job group

[sle][functional][y] implement validation for lvm-full-encrypt and lvm-encrypt-separate-boot test suites

Added by riafarov over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Enhancement to existing tests
Target version:
SUSE QA tests - Milestone 23
Start date:
2018-10-25
Due date:
2019-03-26
% Done:

0%

Estimated time:
Difficulty:
Duration: 109

Description

See motivation in the parent ticket.

We have lvm-full-encrypt, lvm-encrypt-separate-boot and they both run standard set of test modules, which doesn't make sense. What we need to validate is lvm and encryption setup

Acceptance criteria

  1. Only relevant test modules are scheduled for lvm-full-encrypt, lvm-encrypt-separate-boot for SLE and openSUSE
  2. Partitioning is validated after installation for SLE and openSUSE

History

#1 Updated by riafarov over 1 year ago

  • Subject changed from [sle][functional][y] implement validation for enctypt lvm test suites to [sle][functional][y] implement validation for encrypt lvm test suites

#2 Updated by okurz over 1 year ago

  • Category set to Enhancement to existing tests
  • Target version set to future

I see the reason for this ticket and the benefit but I would suggest to collect experience with the existing "validation" scenarios first and keep the ones you mentioned as long as they do not fail and make us problems. I don't see a problem in general to run the proven scenarios for the time being.

#3 Updated by riafarov over 1 year ago

  • Parent task changed from #42854 to #42494

#4 Updated by okurz over 1 year ago

  • Target version changed from future to Milestone 23

#5 Updated by riafarov over 1 year ago

  • Due date set to 2019-02-26

#6 Updated by riafarov over 1 year ago

  • Estimated time set to 5.00 h

INSTALLATION_VALIDATION variable can be used here for scheduling

#7 Updated by ybonatakis over 1 year ago

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

#8 Updated by riafarov over 1 year ago

  • Copied to action #48173: [sle][functional][y] implement validation for encrypt lvm test suites added

#9 Updated by riafarov over 1 year ago

  • Copied to deleted (action #48173: [sle][functional][y] implement validation for encrypt lvm test suites)

#10 Updated by riafarov over 1 year ago

  • Start date set to 2018-10-25

due to changes in a related task

#11 Updated by riafarov over 1 year ago

  • Subject changed from [sle][functional][y] implement validation for encrypt lvm test suites to [sle][functional][y] implement validation for lvm-full-encrypt and lvm-encrypt-separate-boot test suites

#12 Updated by ybonatakis over 1 year ago

  • Status changed from In Progress to Feedback

#13 Updated by riafarov over 1 year ago

  • Due date set to 2019-03-26

Somehow due date got unset. So, if we want to proceed with Test-Assert package, I've created 5 SR:
https://build.opensuse.org/request/show/683934
https://build.opensuse.org/request/show/683935
https://build.opensuse.org/request/show/683936
https://build.opensuse.org/request/show/683937
https://build.opensuse.org/request/show/683938

We also need to enable arm and power architectures for those.
For o3 workers, these packages are already installed.

#14 Updated by ybonatakis over 1 year ago

  • Status changed from Feedback to Resolved

#16 Updated by ybonatakis over 1 year ago

  • Status changed from Resolved to In Progress

Reopening this ticket to address the problem which appears in https://openqa.suse.de/tests/2685364#step/validate_lvm_encrypt/139.

the script_retry doesnt seem to be sufficient as the syncs of the dfs are random.
An explicit sync would be a better approach.

#17 Updated by ybonatakis over 1 year ago

  • Status changed from In Progress to Feedback

#18 Updated by JERiveraMoya over 1 year ago

  • Status changed from Feedback to In Progress

PR merged, please retrigger VR and resolve the ticket if succeeds.

#19 Updated by ybonatakis over 1 year ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF