Route is not populated correctly when next hop moves

When the next hop moves from [1A,1B] to [1A],
there should be a route on 1B pointing to 1A via spines

Change-Id: I817414fb4e9edf29357fdb5e55675537ff5f0cac
(cherry picked from commit 53eae194a8b66287855483359309597e8df2efa9)
2 files changed
tree: ef672bbedaaa600a32743f160caa2f095b9319ab
  1. BUILD
  2. app/
  3. web/