tree ef672bbedaaa600a32743f160caa2f095b9319ab
parent a7601c9d9795e796bfa9b3fec9cb20e21cfa306f
author Charles Chan <rascov@gmail.com> 1551397257 -0800
committer Pier Luigi Ventre <pier@opennetworking.org> 1552688889 +0000

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)