On Mon, Oct 22, 2012 at 7:39 AM, <Paul.Goessinger(a)dab.com> wrote:
Hi,
We are using cobber to manage our machines for our satellite. Re are using
satellite 5.5 with cobbler 2.0.7. Since our last upgrade, our VMWare
Machines do not use the static IP anymore during kickstart.
NOTICE NetworkManager: ifcfg-rh: Ignoring connection 'System eth0' and
its device due to NM_CONTROLLED/BRIDGE/VLAN.
Before the upgrade, this worked.
We use this cobbler command to add the machine:
cobbler system add --name=thename --profile=theprofilename
--hostname=thename --kopts="ksdevice=eth0 umgebung=LAN" --interface=eth0
--static=true --mac=00:50:56:9b:2e:c6 --ip=6.7.8.9 --subnet=255.255.255.0
--gateway=3.4.5.6 --name-servers=1.2.3.4
What are we doing wrong? I searched for different combinations of cobbler,
NetworkManager, DHCP etc. but I did not find any usable answer. I hope this
is a cobbler problem.
It would seem NetworkManager is interfering, eth0 doesn't exist
(em0/1?) or the MAC for that interface is incorrect. You can try
adding NM_CONTROLLED=no to the pre_install_network_config snippet (and
to the post version as well), though it may depend on during what
state of the kickstart it's trying to request a DHCP address.
Are you kickstarting RH guests on VMware hosts, or using
cobbler/satellite to kickstart the VMware host itself?