In the case of a switch recycle, the connected nic will go down and up
but the communication will restore after the switch is up and running.
This could take a few seconds (much longer than anticipated).
This holds off the i/f state update to the peer.
Also remove the batching interface failover state change. This is already
handled in the failover fsm fail_pending state.
Change-Id: Ia810927dbbc4b3821f7915e6a42bceeac43d9e46
Closes-Bug: 1845393
Signed-off-by: Bin Qian <email address hidden>
Reviewed: https:/ /review. opendev. org/686222 /git.openstack. org/cgit/ starlingx/ ha/commit/ ?id=fc0828238ff 7b670c1d03f97a7 a814f431d756a1
Committed: https:/
Submitter: Zuul
Branch: master
commit fc0828238ff7b67 0c1d03f97a7a814 f431d756a1
Author: Bin Qian <email address hidden>
Date: Wed Oct 2 13:03:09 2019 -0400
Bug1845393 remove interface recovering state
In the case of a switch recycle, the connected nic will go down and up
but the communication will restore after the switch is up and running.
This could take a few seconds (much longer than anticipated).
This holds off the i/f state update to the peer.
Also remove the batching interface failover state change. This is already
handled in the failover fsm fail_pending state.
Change-Id: Ia810927dbbc4b3 821f7915e6a42bc eeac43d9e46
Closes-Bug: 1845393
Signed-off-by: Bin Qian <email address hidden>