Description of problem: Bonded interface ifcfg- files are malformed Version-Release number of selected component (if applicable): foreman-1.6.0.44-6.el6ost.noarch How reproducible: Build on a host with multiple interfaces to bond Steps to Reproduce: 1.Select two interfaces to bond 2.set the mode to 802.3ad 3.drag networks to the bonded interface 4.then do a build. Actual results: you will see ifcfg-.300 files in /etc/sysconfig/network-scripts rather than a ifcfg-bond0.300 file as one would expect. the bond0 does not start (DHCP is not available on that VLAN) and the other interfaces fail to start. the config file has the same incorrect device name (as if there is an empty variable for the bond0 name) Expected results: a ifcfg-bond0.300 file is create with the proper device in it Additional info: this is on a test build for 8.2 beta that NetApp was given
Jeff, This looks like it will be fixed in the A2 release. Thanks for reporting this. --Colin Devine
Verified: rhel-osp-installer-0.4.7-1.el6ost.noarch ruby193-rubygem-staypuft-0.4.13-1.el6ost.noarch ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el6ost.noarch openstack-foreman-installer-2.0.32-1.el6ost.noarch openstack-puppet-modules-2014.1-24.el6ost.noarch Verified that: 1. ifcfg-bond0 configuration file was created under /etc/sysconfig/network-scripts/ 2. It has the proper device name in it "DEVICE="bond0"" 3. The bond and the other interfaces started.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2014-1800.html
This bug is still present in the A2 release> I just tested it my ifcfg files are as follows: ifcfg-.300 ifcfg-.3002 ifcfg-.500 ifcfg-bond0 with the device contained within them as .300 instead of bond0.300
I found the source of this bug on my deployment in the /tmp/ks-script-oSI4Cn script: # bond0.300 interface real=`ip -o link | grep | awk '{print $2;}' | sed s/:$//` the above code greps for a blank mac address, and obviously comes up with no interface name - this then propagates down through the interface config file names and devices within them (being blank)
Please try with latest builds
Verified: Environment: ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el7ost.noarch openstack-foreman-installer-3.0.8-1.el7ost.noarch ruby193-rubygem-staypuft-0.5.9-1.el7ost.noarch rhel-osp-installer-client-0.5.4-1.el7ost.noarch openstack-puppet-modules-2014.2.8-1.el7ost.noarch rhel-osp-installer-0.5.4-1.el7ost.noarch running "ls /etc/sysconfig/network-scripts/ifcfg*|grep bond" results in: /etc/sysconfig/network-scripts/ifcfg-bond0 /etc/sysconfig/network-scripts/ifcfg-bond0.300 The DEVICE line looks as following: DEVICE="bond0.300"