Bug 1032801 - debugging incomplete kickstart files in cmdline mode is hard
Summary: debugging incomplete kickstart files in cmdline mode is hard
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Chris Lumens
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-20 21:17 UTC by Chris Lumens
Modified: 2014-06-18 01:44 UTC (History)
1 user (show)

Fixed In Version: anaconda-19.31.41-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 12:29:07 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Chris Lumens 2013-11-20 21:17:48 UTC 
anaconda will give you the following unhelpful error message:

RuntimeError: Can't have a question in command line mode!

Okay, but what is required to get past this message?  I've got a patch on the list that will print out the names of all the spokes that require information.  That way, the user knows what they're missing.
Comment 2 Jan Stodola 2014-01-30 09:01:48 UTC 
Retested with anaconda-19.31.51-1.el7 with kickstarts missing:

* rootpw
* packages section
* partitioning

In all cases, anaconda printed what information is missing and rebooted after some timeout.

Moving to VERIFIED.
Comment 3 Ludek Smid 2014-06-13 12:29:07 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.