NH not programmed in kernel and struck in TEMP state

[Praveen]

Hi Praveen,
   In one of the setup Ajay reported a issue where flow were going to hold state.
Flow were not programmed because its corresponding rpf next hop was not programmed.

When I dumped the nh entries in ksync, I found it was stuck in TEMP state.

Potential steps that let to this state
1> NH was in kernel in sync state.
2> NH delete was sent to kernel, and NH was in DEL_ACK wait state.
3> Before DEL_ACK was received, a reference to NH was added(May be route addition due to interface activation)
4> DEL_ACK was received, NH goes to TEMP state
5> NH add is notified to ksync, state machine is not triggered because there is not change in NH.

I wrote a test which relatively confirms this.
Let us know ur thoughts.

Regards
Naveen N