Minor fix and Enable the disk encryption for 'mvp-user-trial' profile #1420
Minor fix and Enable the disk encryption for 'mvp-user-trial' profile #1420brianmcgillion merged 2 commits intomainfrom
Conversation
When running the 'extendpersist' service, I encountered the following error: "This disk is currently in use - repartitioning is probably a bad idea." Therefore, we will revert to the previous method of resizing using postBootCommands. Signed-off-by: Vunny Sodhi <vunny.sodhi@unikie.com>
485ddcf to
46bd566
Compare
|
@hros-tii please review. |
Now persist partitioning will be LUKS encrypted. Signed-off-by: Vunny Sodhi <vunny.sodhi@unikie.com>
|
Looks good! |
46bd566 to
0d06126
Compare
|
@milva-unikie @leivos-unikie how will this affect the automated testing setups? |
If that disk encryption is enabled only in release image then I think it won't affect test automation. In release image ssh connection is disabled, so we can not automatically test that anyways. |
Thanks @leivos-unikie for the confirmation. To clarify, disk encryption will be enabled also in debug builds, but there won't be any prompt asking for a TPM PIN as per check here The startup sequence for debug builds will remain unchanged. |
|
Tested on Darter Pro (debug and release, new images)
Also quickly checked that the |
Description of Changes
tpm_clearcommand fromluks-enroll-tpm-unit-scriptas its of no use.When running the
extendpersistservice, I encountered the following error:partResizeScript[1145]: This disk is currently in use - repartitioning is probably a bad idea.Therefore, we will revert to the previous method of resizing using postBootCommands. more details in PR#1232
mvp-user-trialprofileNow persist partitioning will be LUKS encrypted.
Type of Change
Related Issues / Tickets
Checklist
make-checksand it passesTesting Instructions
Applicable Targets
aarch64aarch64x86_64x86_64x86_64Installation Method
nixos-rebuild ... switchTest Steps To Verify:
sda3which is/swapwill not be randomly encypted. It will useLUKSencryptionsda5which is/persistnow will be changed tocryptfile system.Monitor logs
luks-enroll-tpmservice, make sure it don't have any errors[ghaf@ghaf-host:~]$ journalctl -efu luks-enroll-tpmThere will no change in
debugbuilds startup sequence.There will be change in
releasebuilds startup sequence.a. On first boot user will be prompted to
Please enter TPM2 PIN:need to enter any PIN two times to set it and thenpassword.b. On subsequent boots, everytime need to enter
TPM2 PINand thenpassword.Make sure it doesn't break any
Automation use casesor anyCI/CDbuilds.