Bug 1371363

Summary:	anaconda-ks.cfg not generated as expected.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Marcus West <mwest>
Component:	rhev-hypervisor-ng	Assignee:	Fabian Deutsch <fdeutsch>
Status:	CLOSED DUPLICATE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.0.0	CC:	dfediuck, gklein
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	rhev-h / ovirt-node issues
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-30 06:17:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Node	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Marcus West 2016-08-30 03:53:27 UTC

Description of problem:

I'd like to use /root/anaconda-ks.cfg as a kickstart file to do further hypervisor installs, but it doesn't seem to reflect any of the choices I have made.  File datestamp indicates it has not been created recently.

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

RHVH-4.0-20160822.8-RHVH-x86_64-dvd1.iso

How reproducible:

Always

Steps to Reproduce:
1. Do a rhv-h install
2. check /root/anaconda-ks.cfg

Actual results:

File should reflect install options made, and be useable to install subsequent rhv-h servers

Expected results:

/root/anaconda-ks.cfg seems to be static (different to install changes) and dated Aug 18


Additional info:

Comment 2 Fabian Deutsch 2016-08-30 06:17:33 UTC

The existence of an old anaconda-ks.cfg in /root is a build artifact and is a dupe of bug 1324219.

Once that is fixed, the kickstart used during installation should appear.

*** This bug has been marked as a duplicate of bug 1324219 ***