tree aac0b04b06040349cd1732cef6de024532d0bd6d
parent f642fe32c4d73d36c1decae20114a9f3a99ce966
author Charles Chan <rascov@gmail.com> 1551397257 -0800
committer Pier Luigi Ventre <pier@opennetworking.org> 1552688857 +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