Hide Forgot
Description of problem: When doing linux bonding and specifying the bonding mode under BondingOptions in the heat template. If this line contains a syntax error, the default bond set up on the overcloud node defaults to balance-roundrobin. This causes switch issues since this bonding mode requires special switch configuration. This may be a default behaviour of the RHEL 7 operating system. Version-Release number of selected component (if applicable): OSP 8. How reproducible: Everytime Steps to Reproduce: 1. Edit a node template yaml file and create a bond 2. set bonding_options to an value with a syntactical error in it such as "mode=active-backup,miimon=100" instead of "mode=active miimon=100" Actual results: A bond is created with the value specified by bonding_options, but the running bond is a round robin bond instead as reported by /proc/net/bonding/* Expected results: Should default to a safer bonding mode such as active-passive that requires no special switch configuration. Additional info:
There really isn't much we can do here, since the problem occurs in the network initscripts (the default bonding method is built-in to the bonding driver in the kernel). Picking a different default bonding mode when a syntax error occurs is likely to lead to silent configuration of the wrong settings, leading to troubleshooting problems. I would rather the deployment fail if the bonding mode wasn't recognized. It would be better to fail with a warning if the bond mode wasn't formatted correctly. Perhaps this could be addressed in tripleo-validations, but this bug can't be implemented as requested.