QA » openQA Project » openQA Tests » qe-yam

Once we moved from main.pm to corresponding schedules cryptlvm and crypt_no_lvm scenarios, we noticed some complicated block of conditions in lib/utils.pm
According to comments of this method, 'storage-ng' by default puts the boot partition within the encrypted LVM same as in test scenarios where we explicitly create an LVM including boot (C)

For now FULL_LVM_ENCRYPT has been set to these two scenarios at the level of test suites, but we should find a better way to deal with it without using this complicated branching.

Solution should cover all the architectures.

Note: when editing is_storage_ng to include TW we broke previous conditions and was reverted, so a more fixed solution with new modules isolating the logic should help here.