Bug 114955

Summary:	RHEL 2.1 AS kickstart profile points to RHEL 3 AS tree
Product:	Red Hat Satellite 5	Reporter:	Chris Runge <crunge>
Component:	Provisioning	Assignee:	Robin Norwood <robin.norwood>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	johnsond, rhn-bugs
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	rhn360	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-09-30 15:15:47 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:	114644

Description Chris Runge 2004-02-04 20:29:59 UTC

Description of problem:

I've synced 3 channels: RHEL 2.1 AS, RHEL 3 AS, RHEL 3 WS
I've created 3 kickstart profiles, in the following order: RHEL 3 WS,
RHEL 3 AS, and RHEL 2.1 AS

The RHEL 3 WS/AS profiles can be kickstarted. The RHEL 2.1 AS profile,
however, cannot. The kickstart script points to the RHEL 3 AS tree for
some reason. Here's the line from the Kickstart script:

url --url http://rhnsat.vmware/kickstart/dist/ks-rhel-i386-as-3/

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

rhn-satellite-3.0.9-11

How reproducible:

100% thus far. I've deleted and recreated the 2.1 profile several
times and can't fix this.

Comment 1 Dave Johnson 2004-02-05 00:40:32 UTC

I've had the exact same problem when trying to kickstart RHEL 2.1 ES
Update 3.  The kickstart script is generated to point to RHEL 3 AS. 
One difference between my environment and Chris', is that I have only
created a kickstart profile for RHEL 2.1 ES, and not RHEL 3 at all.  I
can also reproduce this at will.

Comment 2 Chris Runge 2004-02-05 02:57:59 UTC

It looks like I was wrong about the RHEL 3 WS being correct after
all... it works, but afterwards systems have RHEL 3 AS as their base
channel. I looked at the kickstart script and sure enough it points to
RHEL 3 AS.

On a related note, I can't find where on the system the Kickstart
scripts are located to manually override this.

Comment 3 Bret McMillan 2004-02-05 16:06:16 UTC

Could it possibly be that the External Location set on this page:
/network/systems/provisioning/trees/edit-tree.pxt

points at a 3AS distribution instead of a 3WS?

Also make sure the kickstart profile being used points to the correct
Distribution:
/network/systems/provisioning/kickstarts/details.pxt

Comment 4 Robin Norwood 2004-02-05 16:22:27 UTC

Ok, this is fixed in CVS.  We were re-writing the URL correctly for
scheduled sessions, but not for kickstarts by label.
 
Chris: The kickstart config files are not stored on the filesystem -
they are dynamically generated at the time they're requested.