Red Hat Bugzilla – Bug 114955
RHEL 2.1 AS kickstart profile points to RHEL 3 AS tree
Last modified: 2007-08-06 14:57:30 EDT
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):
100% thus far. I've deleted and recreated the 2.1 profile several
times and can't fix this.
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.
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.
Could it possibly be that the External Location set on this page:
points at a 3AS distribution instead of a 3WS?
Also make sure the kickstart profile being used points to the correct
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.