Hide Forgot
Lesson Learned: Do not use linux_bridges with linux_bonds for LACP in RHOSP Result: creates looping in the switches when the nics first come online during deployment causing ports to be shutdown Recommendation: Documentation should have a note that for LACP configuration, use of Linux Bridges will cause this looping behavior There is a note about the problems caused by using ovs_bonds with LACP, but it doesn't talk about what to do with the bridges (ovs or linux)? https://access.redhat.com/documentation/en/red-hat-openstack-platform/9/single/networking-guide/#configure_lacp_port_aggregation Step 2 has a mention to OVS Bridge, but that's the only place I see it. I would think it would be good to add a note in this section about not using linux_bridges because it creates loops on the switches when the nics come online https://access.redhat.com/documentation/en/red-hat-openstack-platform/9/single/director-installation-and-usage/#appe-Bonding_Options
Created attachment 1212236 [details] Failing Templates which use combination of linux_bonds and linux_bridges for LACP
Created attachment 1212237 [details] Working templates which use ovs_bridges and linux_bonds with LACP mode=4
After some discussion and link checking, I am closing this bug, as OSP 9 is EOL and 10 has explicit configuration section for bonding options: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html/advanced_overcloud_customization/appe-bonding_options