Back to bug 695345
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| David Cantrell | 2011-04-12 15:00:30 UTC | Assignee | anaconda-maint-list | hamzy |
| Ben Levenson | 2011-05-12 09:25:41 UTC | CC | benl | |
| Suzanne Logcher | 2011-05-16 15:11:23 UTC | CC | syeghiay | |
| Suzanne Logcher | 2011-05-16 20:23:26 UTC | Blocks | 705163 | |
| David Cantrell | 2011-05-16 21:00:16 UTC | CC | hamzy | |
| Assignee | hamzy | dcantrell | ||
| David Cantrell | 2011-05-23 19:50:49 UTC | Blocks | 707042 | |
| David Cantrell | 2011-05-23 19:51:10 UTC | Blocks | 707042 | |
| Depends On | 707042 | |||
| RHEL Program Management | 2011-05-23 19:54:56 UTC | Status | NEW | CLOSED |
| Resolution | --- | WONTFIX | ||
| Last Closed | 2011-05-23 15:54:56 UTC | |||
| Jack Reed | 2011-10-03 02:10:01 UTC | Blocks | 742820 | |
| Stephen Gilson | 2015-04-16 17:53:15 UTC | CC | dcantrell | |
| Flags | needinfo?(dcantrell) | |||
| Laura Bailey | 2015-04-17 08:06:01 UTC | Docs Contact | pbokoc | |
| David Cantrell | 2015-04-21 14:34:48 UTC | CC | sbueno | |
| Flags | needinfo?(dcantrell) | |||
| Samantha N. Bueno | 2015-04-21 15:02:05 UTC | Doc Text | On s390x systems, you cannot use automatic partitioning and encryption. If you want to use storage encryption, you must perform custom partitioning. Do not place the /boot volume on an encrypted volume. | Cause: If a user chooses automatic partitioning with encryption on s390x, /boot is created on LVM, where PVs are encrypted. Consequence: An error occurs showing that you can not have a bootable partition on an encrypted device. Workaround (if any): If you want to use storage encryption, you must perform custom partitioning. Do not place the /boot volume on an encrypted volume. Result: Users are able to perform an encrypted installation successfully. |
| Doc Type | Bug Fix | Known Issue | ||
| Petr Bokoc | 2015-04-22 14:33:49 UTC | Doc Text | Cause: If a user chooses automatic partitioning with encryption on s390x, /boot is created on LVM, where PVs are encrypted. Consequence: An error occurs showing that you can not have a bootable partition on an encrypted device. Workaround (if any): If you want to use storage encryption, you must perform custom partitioning. Do not place the /boot volume on an encrypted volume. Result: Users are able to perform an encrypted installation successfully. | Automatic partitioning on IBM System z does not work with LUKS When using automatic partitioning (the 'autopart' Kickstart command or its equivalent in the graphical interface) and enabling full disk encryption with LUKS at the same time, /boot will be created as a LVM logical volume on an encrypted physical volume. This results in an unbootable system. To work around this issue, create a custom partition layout using Kickstart or the graphical interface. |
| Hanns-Joachim Uhl | 2015-05-05 15:53:40 UTC | CC | hannsj_uhl | |
| Petr Bokoc | 2015-06-24 11:37:50 UTC | Doc Text | Automatic partitioning on IBM System z does not work with LUKS When using automatic partitioning (the 'autopart' Kickstart command or its equivalent in the graphical interface) and enabling full disk encryption with LUKS at the same time, /boot will be created as a LVM logical volume on an encrypted physical volume. This results in an unbootable system. To work around this issue, create a custom partition layout using Kickstart or the graphical interface. | Automatic Partitioning on IBM System z Does Not Work with LUKS When using automatic partitioning (the 'autopart' Kickstart command or its equivalent in the graphical interface) and enabling full disk encryption with LUKS at the same time, /boot will be created as a LVM logical volume on an encrypted physical volume. This results in an unbootable system. To work around this issue, create a custom partition layout using Kickstart or the graphical interface. |
Back to bug 695345