Description of problem: when creating network for each node end creating bond, the staypuft server change the type of the bond after submit.when trying to fix it again from the network tab under hosts>all-hosts>"host">edit, where the bond configuration is and then submiting and checking again i see that the changes havn't saved. on the host (after i hit deploy..) i see: [root@mac441ea1733d43 ~]# cat /etc/sysconfig/network-scripts/ifcfg-bond0 BOOTPROTO="none" DEVICE="bond0" ONBOOT=yes PEERDNS=no PEERROUTES=no DEFROUTE=no TYPE=Bond BONDING_OPTS="miimon=100 mode=balance-tlb" BONDING_MASTER=yes NM_CONTROLLED=no when i want to see "BONDING_OPTS="miimon=100 mode=802.3ad"" that happened on at least on one host each deployment. (it's depend if i configured the networks/bonds to all nodes at the same time or one by one) Version-Release number of selected component (if applicable): rhel-osp-installer-client-0.5.4-1.el7ost.noarch libreport-rhel-2.1.11-10.el7.x86_64 rhel-osp-installer-0.5.4-1.el7ost.noarch How reproducible: 5/5 Steps to Reproduce: 1.create ha deployment 2.configure the networks and bond to each server and change the type of the bond to 802.3ad. 3.check the results at hosts>all-hosts>"host">edit>network Actual results: the results are that staypuft configure what seems to be the default type of bond (balance-tlb) and not the type that i have Chosen.
PR available: https://github.com/theforeman/staypuft/pull/397
Merged upstream
Verified on: #rpm -qa|grep installer foreman-installer-1.6.0-0.2.RC1.el7ost.noarch rhel-osp-installer-client-0.5.5-2.el7ost.noarch openstack-foreman-installer-3.0.10-2.el7ost.noarch rhel-osp-installer-0.5.5-2.el7ost.noarch
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-2015-0156.html
*** Bug 1191242 has been marked as a duplicate of this bug. ***