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 1215689 - traceback on kickstart --encrypted without --passphrase=
Summary: traceback on kickstart --encrypted without --passphrase=
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-27 13:27 UTC by Jiri Jaburek
Modified: 2015-07-09 13:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-09 13:49:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
simple kickstart reproducer (421 bytes, text/plain)
2015-04-27 13:27 UTC, Jiri Jaburek 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1213096 0 unspecified CLOSED Traceback during kickstart with --encrypt and no --passphrase, no prompt for PP:Skipping sanity check in GUI 2021-02-22 00:41:40 UTC

Internal Links: 1213096

Description Jiri Jaburek 2015-04-27 13:27:20 UTC 
Created attachment 1019329 [details]
simple kickstart reproducer

Description of problem:

The kickstart reference,
https://github.com/rhinstaller/pykickstart/blob/master/docs/kickstart-docs.rst#part-or-partition
mentions

===============================================
--passphrase=

    Specify the passphrase to use when encrypting this partition. Without the above --encrypted option, this option does nothing. If no passphrase is specified, the default system-wide one is used, or the installer will stop and prompt if there is no default.
===============================================

The installer however doesn't show any password prompt and fails on traceback:

anaconda 19.31.123-1 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.7/site-packages/blivet/formats/luks.py", line 230, in create
    raise LUKSError("luks device has no key/passphrase")
  File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 569, in execute
    options=self.device.formatArgs)
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 360, in processActions
    action.execute(callbacks)
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 368, in doIt
    self.devicetree.processActions(callbacks)
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 219, in turnOnFilesystems
    storage.doIt(callbacks)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 185, in doInstall
    turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall, callbacks=callbacks_reg)
  File "/usr/lib64/python2.7/threading.py", line 764, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 211, in run
    threading.Thread.run(self, *args, **kwargs)
LUKSError: luks device has no key/passphrase


Version-Release number of selected component (if applicable):
RHEL-7.1, anaconda-19.31.123-1.el7.x86_64
(tested on x86_64, but likely occurs on other arches as well)

How reproducible:
always

Steps to Reproduce:
1. start a RHEL-7.1 installer with attached ks=http://host/path/to/ks
2. observe graphic installer start up
3. see "An unknown error has occured" error dialog

Actual results:
the installer stops on traceback

Expected results:
the installer asks the user for a password via a dialog box

Additional info:
Comment 3 Jiri Jaburek 2015-04-27 13:34:40 UTC 
Please note that specifying empty --passphrase= has the same effect as not specifying --passphrase at all.
Comment 4 David Cantrell 2015-07-09 13:49:52 UTC 
Using the example kickstart in the opening comment, I am unable to reproduce the problem described.  I am using the RHEL-7.2-20150709.n.0 nightly tree.  The installation starts and does not proceed to the second hub, but places the action required icon on the Storage spoke.  When I go there it presents the first storage screen where I click Done and it takes me to custom partitioning where I click Done again and it prompts me to set a LUKS passphrase.  Once I am back at the first hub, I click Begin Installation and the system installs as expected.

This was likely resolved with the rebase of anaconda in 7.2.
Note You need to log in before you can comment on or make changes to this bug.