StarlingX

  1. Bug #1885582
  2. Comment #3

Comment 3 for bug 1885582

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ansible-playbooks (master)

Reviewed: https://review.opendev.org/738720
Committed: https://git.openstack.org/cgit/starlingx/ansible-playbooks/commit/?id=075d3fcdfcc0e3e3480918fde22d16163df401ab
Submitter: Zuul
Branch: master

commit 075d3fcdfcc0e3e3480918fde22d16163df401ab
Author: Joseph Richard <email address hidden>
Date: Tue Jun 30 15:33:13 2020 -0400

    Use controller-0 ip for calico-node can-reach dest

    Because cluster floating IP host can change, it should not be used for
    calico node address, and doing so has been observed to cause an error
    when calico-node is rebooted on the active controller and then a swact
    is executed, causing BGP peering to be lost.

    This commit switches to using controller-0 cluster host address for
    route selection, in order to ensure a consistent route selection is
    used.

    Closes-Bug: 1885582
    Change-Id: I56c5ddf657eb557b83ce0fd3ce7beb71011d6266
    Signed-off-by: Joseph Richard <email address hidden>