Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Anaconda fails with an error message when re-using existing encrypted PV:
Storage Activation Failed - format has not been created
See steps to reproduce.
Version-Release number of selected component (if applicable):
RHEL-6.7 GA (anaconda-13.21.239-1.el6)
How reproducible:
always
Steps to Reproduce:
1. prepare the following disk layout (default partitioning layout with encryption):
vda
├─vda1 500M part /boot
└─vda2 9.5G part
└─luks-efd8d7b3-47f2-4e07-8e2e-1fffd3d33c56 (dm-0) 9.5G crypt
├─VolGroup-lv_root (dm-1) 8.5G lvm /
└─VolGroup-lv_swap (dm-2) 1G lvm [SWAP]
2. start a new installation
3. enter the password for the encrypted partition when asked
4. proceed to the custom partitioning screen
5. remove the existing VG with LVs
6. edit vda1, mount point /boot, format as ext4, click OK
7. edit vda2, check "Format as: physical volume (LVM)", click OK
8. edit vda2 again, uncheck Encrypt, click OK
9. edit vda2 again, check Encrypt, click OK
10. create LVM VG and LVs for rootfs and swap
11. try to finish the installation
Actual results:
anacoda error after confirming the changes to be written to disk
Expected results:
disk layout created successfully
Additional info:
Not able to reproduce when the steps 8 and 9 are skipped.
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
http://redhat.com/rhel/lifecycle
This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:
https://access.redhat.com/
Description of problem: Anaconda fails with an error message when re-using existing encrypted PV: Storage Activation Failed - format has not been created See steps to reproduce. Version-Release number of selected component (if applicable): RHEL-6.7 GA (anaconda-13.21.239-1.el6) How reproducible: always Steps to Reproduce: 1. prepare the following disk layout (default partitioning layout with encryption): vda ├─vda1 500M part /boot └─vda2 9.5G part └─luks-efd8d7b3-47f2-4e07-8e2e-1fffd3d33c56 (dm-0) 9.5G crypt ├─VolGroup-lv_root (dm-1) 8.5G lvm / └─VolGroup-lv_swap (dm-2) 1G lvm [SWAP] 2. start a new installation 3. enter the password for the encrypted partition when asked 4. proceed to the custom partitioning screen 5. remove the existing VG with LVs 6. edit vda1, mount point /boot, format as ext4, click OK 7. edit vda2, check "Format as: physical volume (LVM)", click OK 8. edit vda2 again, uncheck Encrypt, click OK 9. edit vda2 again, check Encrypt, click OK 10. create LVM VG and LVs for rootfs and swap 11. try to finish the installation Actual results: anacoda error after confirming the changes to be written to disk Expected results: disk layout created successfully Additional info: Not able to reproduce when the steps 8 and 9 are skipped.