Description of problem: Configuring provisioning network on bond fails via tripleO templates . members: - type: ovs_bond name: bond-prov ovs_options: {get_param: BondInterfaceOvsOptions} members: - type: interface name: em1 primary: true - type: interface name: em2 The node gets written with image but the network configuration seen after reboot makes it inaccessible . em1 seems to have dhcp IP address , but em2 seems to have discovery IP address . The stack create seems to be stuck indefinitely . Version-Release number of selected component (if applicable): RHOS7 OSPD7 openstack-tripleo-heat-templates-0.8.6-71.el7ost.noarch openstack-tripleo-0.0.7-0.1.1664e566.el7ost.noarch Due to discovery IP on em2 , cannot ssh from director to em1 / dhcp IP . How reproducible: Not confirmed . Steps to Reproduce: 1. Configure controllers with 2 nics as bond . 2. 3. Actual results: em1 & em2 are not bonded & em2 has discovery IP & em1 has dhcp IP . Expected results: Bond is created using em1 & em2 & has an accessible IP over dhcp range . Additional info: to access node at this point, we copy ssh private key to compute & ssh from compute . Disabling em2 also allow access to controller at this point .
Created attachment 1094849 [details] network yaml files
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
Bonds on the provisioning network should work, certainly with OSP-Director 7.3+. We do test bonding via the provisioning network. The behavior where some of the bond slaves may receive a discovery IP is transient, and that IP should disappear when the bond is configured.