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 1654475

Summary: Installation fails when manually configuring storage with encrypted root.
Product: Red Hat Enterprise Linux 8 Reporter: Megan Towey <mtowey>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0CC: jkonecny, mtowey
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-30 08:58:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1623566    
Attachments:
Description Flags
All /tmp/*.log files
none
All /tmp/*.log files none

Description Megan Towey 2018-11-28 21:08:05 UTC
Description of problem:
Get an unknown error when attempting to install with encrypted root. 

Version-Release number of selected component (if applicable):


How reproducible:
Every time (4/4 times)

Steps to Reproduce:
1. Select "Encrypt my data." and Custom storage configuration
2. Populate storage configuration automatically(4.39G rhel-root, 1024M sda1 boot, 614M rhel-swap)
3. Set LUKS passphrase
4. Begin installation

Actual results:
Pop up error:
"An unknown error has occurred
This program has encountered an unknown error. You may report the bug below or quit the program."

Expected results:
Installation should complete, creating three logical volumes specified. 

Additional info:
Does not occur if "automatic" storage configuration is selected. Does not occur if encryption is not present.

Comment 1 Megan Towey 2018-11-28 21:39:23 UTC
Neglected to include this information in my original statement:

I am using the RHEL 8.0 public beta image.

Comment 2 Jiri Konecny 2018-11-29 08:48:27 UTC
Could you please attach logs from the installation? You can find them in /tmp/*.log in the installation environment.

Comment 3 Megan Towey 2018-11-29 14:16:53 UTC
Created attachment 1509807 [details]
All /tmp/*.log files

Attaching logs

Comment 4 Megan Towey 2018-11-29 14:19:59 UTC
Created attachment 1509809 [details]
All /tmp/*.log files

Attached wrong tarball earlier. Here is the correct one.

Comment 5 Jiri Konecny 2018-11-30 08:58:07 UTC

*** This bug has been marked as a duplicate of bug 1628519 ***