[et-mgmt-tools] Problem with importing/kickstarting RHEL5.2

[Michael DeHaan]

Ashley Penney wrote:
> Due to hitting a bug in deploying 5.1 (Yum crashes during kickstart) I 
> attempted to import a 5.2 DVD instead.  This works, but the 
> 'retrieving stage2' part of the initial bootup takes about 20-30 
> minutes to chug through.

>
> I looked into this and I found in my errorlog:
>
> Mon Mar 17 06:09:22 2008] [error] [client 10.241.209.34 
> <http://10.241.209.34>] File does not exist: 
> /var/www/cobbler/links/RHEL-52-x86_64/images/updates.img
> [Mon Mar 17 06:09:22 2008] [error] [client 10.241.209.34 
> <http://10.241.209.34>] File does not exist: 
> /var/www/cobbler/links/RHEL-52-x86_64/disc1
> [Mon Mar 17 06:09:22 2008] [error] [client 10.241.209.34 
> <http://10.241.209.34>] File does not exist: 
> /var/www/cobbler/links/RHEL-52-x86_64/images/product.img
> [Mon Mar 17 06:09:22 2008] [error] [client 10.241.209.34 
> <http://10.241.209.34>] File does not exist: 
> /var/www/cobbler/links/RHEL-52-x86_64/disc1
> [Mon Mar 17 06:09:36 2008] [error] [client 10.241.209.34 
> <http://10.241.209.34>] File does not exist: 
> /var/www/cobbler/links/RHEL-52-x86_64/disc1
>
> Where does cobbler define this 'disc1' business?  I grepped everything 
> in site looking for disc1 trying to find out where on earth this comes 
> from.  It's not in /var/www/cobbler as best I can tell, it's not in 
> any kickstart files or /etc/cobbler/.  Can anyone shed light in this?
>

These messages from Anaconda are standard and are not part of the 
problem, you'll see them in most installations.

As to your install slowness, I'm not sure /what/ is causing that, though 
if it has reached kickstart you are outside of Cobbler's territory.  
Perhaps there is something else in your logs that can help you debug this.

You can try checking your kickstarts with "cobbler validateks" (requires 
pykickstart to be installed).

The yum crash should probably be reported in bugzilla under the Anaconda 
component.

--Michael