Experimental (unsupported) enable of upgrades for encrypted devices #1100
Conversation
Upgrades with encrypted devices / partitions are not supported now. Based on the feedback from @Naranthiran, it is possible to upgrade with encrypted devices (using TPM) with the following changes. We have no idea in what all situations this will work correctly, nor detection of used technologies is implemented to say whether the decryption of encrypted devices will happen automatically correctly or not, etc. From this point, allowing the upgrade in unsupported mode when following devel envar is set: LEAPP_DEVEL_ALLOW_DISK_ENCRYPTION=1 For more details, see: oamg#1098 Authored / Co-authored-by @Naranthiran
Thank you for contributing to the Leapp project!Please note that every PR needs to comply with the Leapp Guidelines and must pass all tests in order to be mergeable.
Packit will automatically schedule regression tests for this PR's build and latest upstream leapp build. If you need a different version of leapp from PR#42, use To launch regression testing public members of oamg organization can leave the following comment:
Please open ticket in case you experience technical problem with the CI. (RH internal only) Note: In case there are problems with tests not being triggered automatically on new PR/commit or pending for a long time, please contact leapp-infra. |
|
Closing in favor of #1200 |
Upgrades with encrypted devices / partitions are not supported now. Based on the feedback from @Naranthiran, it is possible to upgrade with encrypted devices (using TPM) with the following changes.
We have no idea in what all situations this will work correctly, nor detection of used technologies is implemented to say whether the decryption of encrypted devices will happen automatically correctly or not, etc. From this point, allowing the upgrade in unsupported mode when following devel envar is set:
For more details, see:
#1098
Authored / Co-authored-by @Naranthiran