action #42941
closedcoordination #40475: [functional][y][saga] Establish YaST team split
coordination #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
0%
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¶
- Only relevant test modules are scheduled for lvm-full-encrypt, lvm-encrypt-separate-boot for SLE and openSUSE
- Partitioning is validated after installation for SLE and openSUSE
Updated by riafarov over 5 years 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
Updated by okurz over 5 years 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.
Updated by okurz over 5 years ago
- Target version changed from future to Milestone 23
Updated by riafarov about 5 years ago
- Estimated time set to 5.00 h
INSTALLATION_VALIDATION variable can be used here for scheduling
Updated by ybonatakis about 5 years ago
- Status changed from Workable to In Progress
- Assignee set to ybonatakis
Updated by riafarov about 5 years ago
- Copied to action #48173: [sle][functional][y] implement validation for encrypt lvm test suites added
Updated by riafarov about 5 years ago
- Copied to deleted (action #48173: [sle][functional][y] implement validation for encrypt lvm test suites)
Updated by riafarov about 5 years 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
Updated by ybonatakis about 5 years ago
- Status changed from In Progress to Feedback
Updated by riafarov about 5 years 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.
Updated by ybonatakis about 5 years ago
- Status changed from Feedback to Resolved
Updated by ybonatakis about 5 years ago
Verification Runs in Production:
https://openqa.suse.de/tests/2574819
https://openqa.suse.de/tests/2574820
https://openqa.suse.de/tests/2574831
https://openqa.opensuse.org/tests/885764
https://openqa.opensuse.org/tests/885765
https://openqa.opensuse.org/tests/885767
https://openqa.opensuse.org/tests/885768
Updated by ybonatakis about 5 years 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.
Updated by ybonatakis about 5 years ago
- Status changed from In Progress to Feedback
Updated by JERiveraMoya about 5 years ago
- Status changed from Feedback to In Progress
PR merged, please retrigger VR and resolve the ticket if succeeds.
Updated by ybonatakis about 5 years ago
- Status changed from In Progress to Resolved