Comment 0 for bug 1885582

Brief Description
-----------------
It was observed that occasionally after a swact, the calico BGP peering is failing.

This is the result of Calico choosing the floating IP on the cluster-host. The unit IP should be used instead. This happens if the calico-node pod restarts on the same host that currently has the floating IP.

If a system is in this condition, a swact results in the floating IP moving, so Calico loses communication with the BGP peers.

Severity
--------
Major - calico issues after swact

Steps to Reproduce
------------------
- Bring up system
- Check address calico is using >> should be the unit IP
- Restart the calico pod on the host w/ the floating IP
- Check the address calico is using >> will not be the floating IP
- Perform a swact
- Verify that calico loses peering with the BGP peers

Expected Behavior
------------------
calico should always use the unit IP address

Actual Behavior
----------------
calico uses the floating IP address if the calico pod is restarted

Reproducibility
---------------
Reproducible given the steps above

System Configuration
--------------------
Any 2-node system

Branch/Pull Time/Commit
-----------------------
Seen on stx master 2020-06-27, but is a day 1 issue

Last Pass
---------
Unknown

Timestamp/Logs
--------------
N/A

Test Activity
-------------
Regression Testing

Workaround
----------