Bug 1297380

Summary: Missing local (file:/) kickstart file with inst.text combination starts the automatic installation
Product: Red Hat Enterprise Linux 7 Reporter: Jiri Konecny <jkonecny>
Component: anacondaAssignee: Brian Lane <bcl>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.3CC: jstodola, mkovarik
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: anaconda-21.48.22.74-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-03 23:21:34 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 Jiri Konecny 2016-01-11 11:08:50 UTC 
Description of problem:
When an installation is started with boot parameters ks=file:/non/existing/path/kickstart.ks and inst.text then it will start automatic install process. For the sake of sanity this should be fixed soon. When there is only typo in the kickstart path it's hard to find out what is happening.

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

How reproducible:
Always

Steps to Reproduce:
1. Start installation with boot options ks=file:/non/existing/path/kickstart.ks and inst.text .
2. The installation stops on error message that you have bad storage.

Actual results:
Installation stops when complaining about bad partitioning.

Expected results:
It should stops on start of the installation with message "Missing kickstart file" or "Kickstart file %s not found".
Comment 2 Brian Lane 2016-05-26 16:19:09 UTC 
https://github.com/rhinstaller/anaconda/pull/646
Comment 4 Michal Kovarik 2016-08-02 10:02:02 UTC 
Verified on anaconda-21.48.22.81-1.
Comment 6 errata-xmlrpc 2016-11-03 23:21:34 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.

https://rhn.redhat.com/errata/RHEA-2016-2158.html