action #72172
Updated by JRivrain over 3 years ago
In the scope of parent ticket, we saw that in some cases we can have a [false positive](https://openqa.suse.de/tests/4727172#step/validate_encrypted_partition_not_activated/2) 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](https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/11042)) 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. ### Acceptance criteria * Device is identified before running "cryptsetup status" against it Or * Another command is used to validate the encryption of the root disk