Bug 623034

Summary:	failed to start kickstart install when provide ks file with hd device path
Product:	[Fedora] Fedora	Reporter:	Liam Li <lili>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	14	CC:	anaconda-maint-list, jlaska, jonathan, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-08-12 03:01:12 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	611991

Description Liam Li 2010-08-11 07:21:55 UTC

Description of problem:
The kickstart install failed to start when follow these steps

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

How reproducible:
always

Steps to Reproduce:
1. copy a kickstart file to /dev/vda1. we can do like this:
* boot install on an installed system, this system should have a /dev/vda1
* when anaconda started, press Ctrl+Alt+F2 to tty2
* mkdir aa; mount /dev/vda1 aa
* scp remote/ks.cfg aa
2. reboot,and restart install, in grub command line, enter: ks=hd:/dev/vda1:/ks.cfg
3.
  
Actual results:
the kickstart install did not start, only anaconda was started. press Ctrl+Alt+F2 to tty2, mount /dev/vda1 /dir, cd /dir to check the ks.cfg, the file was zero, the content of file was lost.

Expected results:
the kickstart install should start

Comment 1 James Laska 2010-08-11 13:14:46 UTC

Good catch Liam!  Are you able to access the installer log files (/tmp/*log)?  If so, can you please attach them to the bug report?  Alternatively, screenshots of tty3, tty4 and tty5 might be okay in a pinch.  Thanks!

Adding to F14Beta per the following beta release criteria:

  "The installer must be able to use all kickstart delivery methods "

Comment 2 Liam Li 2010-08-12 03:01:12 UTC

This may due to a virtual machine's issue, I retested on real machine today, can not reproduce it again, I will have more tests later.SO close it as NOTABUG first. Thanks