Apparently my kickstart doesn’t add NM_CONTROLLED=no to the vlan on a bond.. off to fix.

[root@thisisfine network-scripts]# cat ifcfg-bond0.10

BOOTPROTO=”none”

IPADDR=”10.10.10.10″

NETMASK=”255.255.252.0″

GATEWAY=”10.10.10.1″

DEVICE=”bond0.10″

ONBOOT=yes

PEERDNS=no

PEERROUTES=no

VLAN=yes

NM_CONTROLLED=no

That worked..

However, it just seems that NetworkManager is the culprit.. if you simply do “service NetworkManager stop” and do “service network restart” everything is fine. (not really..)

Anyone else running into similar issues with NetworkManager? Are you simply disabling it entirely by turning it off? are you migrating to using it or are you managing what NetworkManager controls and using it for some things?

Sometimes I really miss the simplicity of just defining an interface and knowing it’s there.. I understand NetworkManager’s role on a desktop/workstation to manage wifi access and “automagically” manage your devices, but on Servers? What is your take? Are you disabling it if you don’t use DHCP? can it safely be disabled or should the tooling grow up around it and let it manage what it expects to manage?