Bug 1032801

Summary:	debugging incomplete kickstart files in cmdline mode is hard
Product:	Red Hat Enterprise Linux 7	Reporter:	Chris Lumens <clumens>
Component:	anaconda	Assignee:	Chris Lumens <clumens>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	jstodola
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	anaconda-19.31.41-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-13 12:29: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:

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.