action #72172
closedcoordination #42854: [functional][y][epic] Introduce relevant installation validation test modules
[functional][y] Make sure we are validating the right device in validate_encrypted_partition_not_activated
0%
Description
In the scope of parent ticket, we saw that in some cases we can have a false positive when probing the encrypted volume:
"the module validate_encrypted_partition_not_activated does "cryptsetup status /dev/mapper/cr-auto-2" and expects to have as a result "/dev/mapper/cr-auto-2 is inactive"
but if I write "cryptsetup status my_grandma", it will also succeed as the output will be "my_grandma is inactive"." (quote from PR)
We can argue that expectations are set in advance, but in case something changes in the packages or in the configuration,that module will do false positives until we notice it.
Run on osd: https://openqa.suse.de/tests/4780271#step/validate_encrypted_partition_not_activated/1
Acceptance criteria¶
- Device is identified before running "cryptsetup status" against it
Or
- Another command is used to validate the encryption of the root disk
Or
- We check that we don't have any activated devices
Or
- We validate that encrypted device exists and validate that it's not activated
Updated by riafarov over 3 years ago
- Project changed from openQA Tests to qe-yam
- Target version set to SLE 15 SP3
- Parent task changed from #69046 to #42854
Updated by riafarov over 3 years ago
- Description updated (diff)
- Status changed from New to Workable
Updated by riafarov over 3 years ago
- Project changed from openQA Tests to qe-yam
Updated by JERiveraMoya over 3 years ago
- Status changed from Workable to In Progress
- Assignee set to JERiveraMoya
Updated by JERiveraMoya over 3 years ago
- Status changed from In Progress to Feedback