Cryptinplace: use persistent device naming #110
Labels
No labels
ACS 4.15
Doing
Regression
To Do
critical
enhancement
major
minor
operations
patch
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
privazio/ansible-collection-vdc#110
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
rented a 2SSD server, each boot the device name changes... seems to break cryptinplace
changed title from {-Hetzner: changing disk devices-} to {+Cryptinplace: use persistent device naming+}
mentioned in commit
10b5d808b4there are additional issues:
Maybe MAAS is using a custom ramdisk or something but in our MAAS environment is OK and hetzner is not
I did not get to understand why the crypto modules are missing in the initramfs
Or why ARE there in our MAAS installed servers
cryptroot hook will try to guess which modules are required, however it can be forced to include all/most editing this file:
and setting
CRYPTSETUP=ymentioned in commit
e7c942cdcb