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.

Bug 702144

Summary: Disk Druid doesn't show "lock" icon when selecting to encrypt existing partiions/LVs
Product: Red Hat Enterprise Linux 6 Reporter: Lamont Peterson <peregrine>
Component: anacondaAssignee: Brian Lane <bcl>
Status: CLOSED NOTABUG QA Contact: Release Test Team <release-test-team-automation>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.0   
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-31 14:03:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lamont Peterson 2011-05-04 21:24:46 UTC
Description of problem:
The user sees a check-mark instead of the lock under the "Format" column when formatting and encrypting an existing LV or partition.

Version-Release number of selected component (if applicable):
RHEL 6.0 -- anaconda 13.??.82 (sorry, forgot the exact number in the middle there).

How reproducible:
Easily.

Steps to Reproduce:
1.  On a system with existing LVs, boot from DVD (or however) and run the GUI installer.
2.  Select manual partitioning.
3.  Edit an existing LV or partition and select the "Encrypt" checkbox.
  
Actual results:
Check-mark shows under the "Format" column for that LV/partition.

Expected results:
Lock shows under the "Format" column for that LV/partition.

Additional info:
Nothing more to say.

Comment 2 RHEL Program Management 2011-05-05 06:02:06 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 3 Brian Lane 2011-05-09 18:16:05 UTC
I cannot reproduce this with 13.21.115

* create custom layout (/boot, LVM with / and swap) none encrypted.
* write partitioning to disk, rebooted install (didn't do a full install)
* edited /boot and selected format+encrypt == lock shows
* edited / lvm and selected format+encrypt == lock shows

You can't select encrypt without first selecting format. If you have a more detailed description of how you did this I can look into it further.

Comment 4 Lamont Peterson 2011-05-23 16:31:09 UTC
The only differences in what I did were:

1.  The initial creation of the partition(s)/LVs included encrypting them.
2.  I actually completed that installation.

Otherwise, you've done the steps that I went through.  Maybe (1) would have an impact but I doubt that (2) matters.