Hide Forgot
Description of problem: Anaconda fails to create automatic partitioning when encryption is enabled. The following message is shown: The following errors occurred with your partitioning: Bootable partitions cannot be on an encrypted block device Bootable partitions cannot be on an encrypted block device Bootable partitions cannot be on an encrypted block device This can happen if there is not enough space on your hard drive (s) for the installation. Press 'OK' to choose a different partitioning option. It seems that anaconda is trying to place /boot into LVM, where PVs are encrypted. When the warning message is shown, user can go back and create custom partitioning with /boot on an unencrypted partition and rest of filesystems encrypted. Version-Release number of selected component (if applicable): RHEL6.1-20110406.0 anaconda-13.21.111-1.el6 How reproducible: always Steps to Reproduce: 1. start graphical installation on s390x 2. enable "Encrypt system" check box at the partitioning type screen 3. continue with the installation Actual results: anaconda cannot create partitioning Expected results: partitioning is created automatically, /root swap and /home are encrypted, boot is not encrypted
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: 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.
New and extended product functionality as well as new features for this component must be implemented by IBM and accepted upstream before consideration for a RHEL backport can be made. For your convenience, this bug has been cloned to the same component under Fedora, which serves as the upstream development area for RHEL.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.
Engineering and Product Management along with CCS have determined that this bug should be described in the RHEL 6.7 Release Notes. Please update the Doc Text field with a description following the Cause Consequence Workaround Result model by April 22.