Comment 0 for bug 1845393

Brief Description
-----------------
After a switch restart, the controllers is unable to establish active-standby relationship. When the switch got restarted; both controllers experienced heartbeat loss on both mgmt and cluster-host interfaces. Before making the fail-over decision; these interfaces went down but the peer update had not been received so both controllers think its peer is more healthy.

Severity
--------
Critical

Steps to Reproduce
------------------
While the system is up with all nodes unlocked-enabled-availabled, restart the switch.

Expected Behavior
------------------
Communications are restored after switch restart. All nodes are unlocked-enabled-available. Horizon is accessible via floating IP.

Actual Behavior
----------------
Access to floating IP is lost. Each controller is in standalone state. Can only ssh into each controller using node IP. Worker nodes are inaccessible.

Reproducibility
---------------
Only tried restarting the switch once an in attempt to resolve the periodic state transition of the bond slaves from ACTIVE to BACKUP that might have caused Multinode Failure Avoidance in the lab.

System Configuration
--------------------
IPv6 Standard system

Branch/Pull Time/Commit
-----------------------
SW_VERSION="19.10"
BUILD_TARGET="Host Installer"
BUILD_TYPE="Formal"
BUILD_ID="2019-09-17_20-00-00"
SRC_BUILD_ID="15"

Last Pass
---------
N/A

Timestamp/Logs
--------------
See sm.log attached

Test Activity
-------------
System Test