On Thu, 2009-10-08 at 16:09 -0400, Michael DeHaan wrote: > On 10/07/2009 11:51 AM, Duncan Innes wrote: > > Hi, > > > > I'm testing this on Satellite 5.3 at the moment, but the inclusion of > > Cobbler appears to break re-provisioning. > > > > My kickstarts use a postinstall script to configure the network scripts > > according to which configuration files are installed by the relevant > > activation keys. Unfortunatley, cobbler seems to write it's own network > > config files and then deletes everything that may have existed proir to > > that. > > > > So I can't even push anything to /etc/sysconfig/network-scripts. > > > > The erroneous part of cobbler.ks is as follows: > > > > %post > > ( > > /opt/edft/bin/postinstall > > ) >> /root/ks-post.log 2>&1 > > > > > > > > > > # Start post_install_network_config generated code > > mkdir /etc/sysconfig/network-scripts/cobbler > > cp /etc/sysconfig/network-scripts/ifcfg-lo > > /etc/sysconfig/network-scripts/cobbler/ > > # Start configuration for eth0 > > IFNAME=$(ifconfig -a | grep -i '00:24:81:E3:F9:78' | cut -d ' ' -f 1) > > if [ -f "/etc/modprobe.conf" ] && [ $IFNAME ]; then > > grep $IFNAME /etc/modprobe.conf | sed "s/$IFNAME/eth0/" > > > > > > /etc/modprobe.conf.cobbler > > > > > > grep -v $IFNAME /etc/modprobe.conf >> /etc/modprobe.conf.new > > rm -f /etc/modprobe.conf > > mv /etc/modprobe.conf.new /etc/modprobe.conf > > fi > > echo "DEVICE=eth0" > /etc/sysconfig/network-scripts/cobbler/ifcfg-eth0 > > echo "HWADDR=00:24:81:E3:F9:78" > > > > > > /etc/sysconfig/network-scripts/cobbler/ifcfg-eth0 > > > > > > echo " >> /etc/sysconfig/network-scripts/cobbler/ifcfg-eth0 > > echo "BOOTPROTO=dhcp" > > > > > > /etc/sysconfig/network-scripts/cobbler/ifcfg-eth0 > > > > > > # End configuration for eth0 > > rm -f /etc/sysconfig/network-scripts/ifcfg-* > > mv /etc/sysconfig/network-scripts/cobbler/* /etc/sysconfig/network-scripts/ > > rm -r /etc/sysconfig/network-scripts/cobbler > > if [ -f "/etc/modprobe.conf" ]; then > > cat /etc/modprobe.conf.cobbler >> /etc/modprobe.conf > > rm -f /etc/modprobe.conf.cobbler > > fi > > # End post_install_network_config generated code > > > > # Start koan environment setup > > echo "export COBBLER_SERVER=vstlbsatx01.edftrading.com" > > > > > /etc/profile.d/cobbler.sh > > > > > echo "setenv COBBLER_SERVER vstlbsatx01.edftrading.com" > > > > > /etc/profile.d/cobbler.csh > > > > > # End koan environment setup > > > > > > wget > > "http://vstlbsatx01.edftrading.com/cblr/svc/op/ks/system/tcplrdacs01.edftrading.com:1"; > > -O /root/cobbler.ks > > wget > > "http://vstlbsatx01.edftrading.com/cblr/svc/op/trig/mode/post/system/tcplrdacs01.edftrading.com:1"; > > -O /dev/null > > > > Is this happening from Spacewalk too? > > > > Duncan > > > > _______________________________________________ > > Spacewalk-devel mailing list > > Spacewalk-devel redhat com > > https://www.redhat.com/mailman/listinfo/spacewalk-devel > > > > Rather than point blame about what you /think/ is wrong, I'd recommend > just stating the problem you are seeing and let us go from there. > In this case, Cobbler is not broken. Your usage of your kickstart > template, however, is incompatible with them. > > Cobbler network objects eliminate the need to have seperate needs to > configuring networking. > > If you are doing your own thing, remove the network snippets from the > Cobbler template. > > --Michael >
First of all I haven't stated that cobbler is broken. This is a corporate Satellite server that has been upgraded from 5.2 to 5.3. Cobbler is the new addition here. All kickstarts have been working well previous to the upgrade. To state my problem: if I boot a machine via PXE or a boot CD ISO and point to a kickstart file on the Satellite, the installs happen properly. It's only when re-provisioning gets used that these Cobbler additions are made to the kickstart. The effect of this is to delete our network config files and replace them with a single eth0 entry that cobbler creates. Our usage of the kickstart template is pretty standard judging by what I've seen at various Satellite customers. We use activation keys to distribute configuration files (including some network config) and to push out custom post install scripts - which are then run by the kickstart %post script. No configuration of cobbler has been made - everything is standard as per the Satellite upgrade. For cobbler to come along and (albeit by design) delete network config files and overwrite them AFTER the kickstart activation keys and %post scripts can't really be described as a desired behaviour for us. We would expect any type of Satellite install (kickstart, reprovisioning etc) to leave a system in exactly the same state. >From having worked at more than one RHN Satellite customer, I can say quite categorically that this behaviour will be a problem. Network configs are regularly pushed out as part of activation keys or tweaked as part of post install scripts. If this behaviour can be turned off, then fine. I'm not making any accusations here - I'm only asking if this was decided to be the new behaviour for Spacewalk/Satellite/Cobbler. Should there be an inconsistency between fresh kickstart installs and re-provisions? Thanks Duncan Innes _______________________________________________ Spacewalk-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-devel
