From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Description of problem:
While trying to process the kickstart the server to be installed
fails to get his kickstart config.
See attached screen shot.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Schedule a kickstart
2. Reboot for kickstart installation
Actual Results: Failed to retrieve ks.cfg.
Expected Results: Successfull retrieval of a ks.cfg.
Created attachment 96666 [details]
Screenshot of the kickstart logging
Looks like an broken config. The last url seems to miss the hostname
Created attachment 96681 [details]
Another try to kickstart via fixed IP
A try to kickstart with a fixed ip failed also.
Are all of these attempts using fixed IP address? Using eth0 or eth1?
Best guess is we've closed this in the latest build.
I think this bug has not been fixed.
I tried to initiate kickstart from rhns-3.1rc1.
The package auto-kickstart-ks-redhat-advanced-server-i386-qu2-1.2-3
was installed on my target system as it supposed to be.
Then the file
was created and grub was configured to use it.
The ks.cfg should be in this file but it was missing and I got an
error screen as in the previousely attached screenshot for fixed IP
Over to chip to see if he can figure out why NRN's auto-kickstart is
pointing to a file instead of to a URL. This seems to be a different
bug from Christian's, however. Christian's bug should be fixed in RC1
re-assign to firstname.lastname@example.org
REOPENED status has been deprecated. ASSIGNED with keyword of Reopened is preferred.
The RHN Satellite 4.x and RHN Proxy 4.x products have reached their end of
life. Please see:
Satellite 4 EOL Errata
RHN Proxy 4 EOL Errata
This bugzilla was reported for an unspecified version of the product, but was created prior to the release of 5.x - as such we assume this bug was reported for the 4.x version of the product - which is no longer supported.
RHN Satellite and Proxy Server 5
General availability: June 26, 2007
We are closing this bugzilla out. If you feel this bug report should be
reviewed again since it is valid for a currently supported product version,
then please feel free to re-open this bug report.