Bug 1436304 - RHEL 7 kickstart text mode installation halts when just --encrypted is mentioned
Summary: RHEL 7 kickstart text mode installation halts when just --encrypted is mentioned
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.3
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Vendula Poncova
QA Contact: Release Test Team
Sharon Moroney
Depends On:
Blocks: 1477664 1557360
TreeView+ depends on / blocked
Reported: 2017-03-27 15:44 UTC by Abhijeet Sadawarte
Modified: 2021-03-11 15:05 UTC (History)
15 users (show)

Fixed In Version: anaconda-
Doc Type: Bug Fix
Doc Text:
Text mode will now prompt for a passphrase if a Kickstart file does not provide one while enabling encryption Prior to this update, if you used the text mode interface with a Kickstart file that enabled disk encryption but did not provide a passphrase, the installation failed with an error. This update prompts the user to provide a passphrase during installation if the partitioning specified in the provided Kickstart file requires one.
Clone Of:
Last Closed: 2018-10-30 07:52:43 UTC
Target Upstream Version:

Attachments (Terms of Use)
Anaconda Log (9.13 KB, text/plain)
2017-09-05 12:12 UTC, Dan Snider
no flags Details
Anaconda Interface Config Log (1.79 KB, text/plain)
2017-09-05 12:13 UTC, Dan Snider
no flags Details
Anaconda Yum Log (15.74 KB, text/plain)
2017-09-05 12:14 UTC, Dan Snider
no flags Details
Anaconda Program Log (15.74 KB, text/plain)
2017-09-05 12:15 UTC, Dan Snider
no flags Details
Anaconda Storage Log (58.41 KB, text/plain)
2017-09-05 12:16 UTC, Dan Snider
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1185466 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Product Errata RHBA-2018:3035 0 None None None 2018-10-30 07:55:12 UTC

Internal Links: 1185466

Description Abhijeet Sadawarte 2017-03-27 15:44:59 UTC
Description of problem:

When RHEL7 is kickstarted in text mode using the following partitioning, it fails with unfinished Disk configuration (Error checking storage configuration) error and would not prompt for luks password as RHEL 6 text mode or RHEL 7 graphical installation.

clearpart --all --initlabel
part /home --fstype=ext4 --size=500  --encrypted	
part /boot --fstype=ext4 --size=200
part swap --size=1000
part / --fstype=ext4 --grow --size=200

In RHEL 6 text mode, this was prompting the user to provide the password and even RHEL7 documentation mentions as follows.

 --encrypted — Specifies that this logical volume should be encrypted, using the passphrase provided in the --passphrase= option. If you do not specify a passphrase, the installation program will use the default, system-wide passphrase set with the autopart --passphrase command, or stops the installation and prompts you to provide a passphrase if no default is set.

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

How reproducible:

Steps to Reproduce:
1. Use the partitioning mentioned above and start the installation in text mode.
2. See the error

Actual results:
anaconda installer fails with "Error checking storage configuration" error and doesn't prompt for luck passphrase 

Expected results:
It should have asked for password for passphrase like RHEL6 and as per documentation.

Additional info:
Similar bug (Bug 1185466) was filed for RHEL 7 graphical installation and resolved with an error but customer is expecting same behaviour in RHEL 7 text mode installation as well.

Comment 2 Samantha N. Bueno 2017-08-03 07:48:13 UTC
Please attach logs to this bug as individual, text/plain attachments. They can be found in /tmp.

Comment 3 Dan Snider 2017-09-05 12:12:43 UTC
Created attachment 1322176 [details]
Anaconda Log

Comment 4 Dan Snider 2017-09-05 12:13:38 UTC
Created attachment 1322177 [details]
Anaconda Interface Config Log

Comment 5 Dan Snider 2017-09-05 12:14:37 UTC
Created attachment 1322178 [details]
Anaconda Yum Log

Comment 6 Dan Snider 2017-09-05 12:15:19 UTC
Created attachment 1322180 [details]
Anaconda Program Log

Comment 7 Dan Snider 2017-09-05 12:16:17 UTC
Created attachment 1322181 [details]
Anaconda Storage Log

Comment 8 Dan Snider 2017-09-05 12:30:33 UTC
(In reply to Samantha N. Bueno from comment #2)
> Please attach logs to this bug as individual, text/plain attachments. They
> can be found in /tmp.

I have attached logs of a kickstarted text installation of RHEL 7.4 on a virtual machine using the following kickstart partitioning scheme:

# System bootloader configuration.
bootloader --location=mbr --boot-drive=vda
clearpart --all --initlabel --drives=vda

# Disk partitioning information.
part /home --fstype=ext4 --size=2048 --encrypted	
part /boot --fstype=ext4 --size=512
part swap --size=1000
part / --fstype=ext4 --grow --size=200

The error I get in Anaconda is:
"LUKS device vda2 has no encryption key"

If I provide a blank --passphrase flag Anaconda dies with the error:
"The following problem occurred on line 40 of the kickstart file:

--passphrase option requires an argument"

Comment 9 Adam Stallard 2017-10-27 22:06:18 UTC
I am experiencing this issue as well. I am using a plaintext passphrase right now, but this is very undesirable as the config is stored on our PXE install server and then shows up in original-ks.cfg in /root. 

Are there plans to implement an encrypted passphrase such as it is done with the root password? I noticed some discussion here years back but haven't found info on the current state of that as of today with centOS 7.

Comment 12 Vendula Poncova 2018-05-03 17:12:44 UTC
Fixed in a pull request: https://github.com/rhinstaller/anaconda/pull/1468

Comment 14 Jan Stodola 2018-07-19 10:40:34 UTC
Verified with anaconda-
Anaconda running in text mode asks for the encryption password. Tested the autopart, part and pv kickstart commands.
Also retested cmdline and graphical installations for possible regressions - no change comparing to RHEL-7.5 GA was found.

Moving to VERIFIED.

Comment 21 errata-xmlrpc 2018-10-30 07:52:43 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.