Description of problem: When a interface is attached to gluster network, vdsm over writes the configuration file and ONBOOT is set to no.Because of this when ever the system reboots the host losts the connectivity with this interface. vdsm output: ------------ ------------ cat /etc/sysconfig/network-scripts/ifcfg-eth0 # Generated by VDSM version 4.17.0-686.git80f86a3.el6 DEVICE=eth0 HWADDR=00:25:90:7c:2f:c2 ONBOOT=no BOOTPROTO=dhcp MTU=1500 DEFROUTE=no NM_CONTROLLED=no Version-Release number of selected component (if applicable): vdsm-4.17.0-686.git80f86a3.el6.x86_64 How reproducible: Always. Steps to Reproduce: 1. create a network called gluster network. 2. Add a node which has more than one interface. 3. Now from the setup host network dialog attach the gluster network to this interface. Actual results: ONBOOT=no Expected results: It should be always ONBOOT=yes since this this is the interface through which all the gluster data traffic will be flowing. Additional info:
Vdsm does that due to its "unified persistence" of network configuration. As a workaround, you can set vdsm.conf's net_persistence=ifcfg. But a proper solution would take place only when bug 1203422 is addressed. *** This bug has been marked as a duplicate of bug 1203422 ***