Bug 667937

Summary:	RFE: Cobbler buildiso menu and ks placement files.
Product:	Red Hat Satellite 5	Reporter:	Kim Borup <kborup>
Component:	New Feature	Assignee:	Stephen Herr <sherr>
Status:	CLOSED DUPLICATE	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	low
Version:	540	CC:	cperry, jfenal
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-04-11 20:57:42 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:	924190

Description Kim Borup 2011-01-07 11:13:20 UTC

Description of problem:

when you do a cobbler buildiso the buildiso automaticly think that it should pull the KS file directly from the Satellite server, an option inside the satellite server or in cobbler it self to select placement from a proxy server instead would be ideal. like say that if you use this kickstart then you have to go trough this proxy server right now to obtain this you will have to edit isolinux.cfg and then rebuild the iso.


Secondly. the ability to point to KS files with ip instead of dns in those zones where you need to install but you dont have dns ready or avariable at all.

Comment 1 Clifford Perry 2011-01-19 22:22:23 UTC

Please note that cobbler buildiso is currently not supported within Satellite. Please see bug 666435 comment #12 for details. 

IF and when we do choose to support cobbler buildiso we will consider this RFE for consideration to implement. 

Cliff

Comment 2 Stephen Herr 2013-04-11 20:57:42 UTC

I am going to mark this as a duplicate of bug 506485. Bug 506485 is basically "make cobbler buildiso work in a supported manner" and I consider this a part of that functionality. I will not these specific concerns in a comment there.

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