Incorrect next-hop actions which may lead to black holing of traffic:

> show route advertising-protocol bgp 172.20.13.1 7.7.7.34 detail | match label
     Route Label: 25
     Entropy label capable
 
> show route label 25
 
mpls.0: 40 destinations, 40 routes (40 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
 
25                 *[VPN/170] 00:12:42, metric2 30000, from 100.100.100.113
                    >  to 100.70.11.1 via ge-0/0/1.0, Swap 107733
                       to 100.70.21.1 via ge-0/0/2.0, Swap 107733

With one core link down to trigger re-convergance:
 
> show route label 25
 
mpls.0: 41 destinations, 41 routes (41 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
 
25                 *[VPN/170] 00:00:01, from 100.100.100.113
                    >  to 100.70.21.1 via ge-0/0/2.0, Pop <<<<<<<<<<<<<<<<<<<< Issue
                       to 100.70.11.1 via ge-0/0/1.0, Swap 100011
25(S=0)            *[VPN/170] 00:00:01, from 100.100.100.113
                    >  to 100.70.21.1 via ge-0/0/2.0, Pop <<<<<<<<<<<<<<<<<<<< Issue
                       to 100.70.11.1 via ge-0/0/1.0, Swap 100011

The correct behavior:

> show route label 25                                                             
 
mpls.0: 38 destinations, 38 routes (38 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
 
25                 *[VPN/170] 00:00:09, from 100.100.100.113
                    >  to 100.70.21.1 via ge-0/0/2.0, Swap 107734
                       to 100.70.11.1 via ge-0/0/1.0, Swap 107734, Push 100011(top)

Traffic can be black holed due to wrong NH action.

Improper handling of the following cases::

 - inet.0 LISIS route with unlabeled primary nexthop-legs, but labeled backup-legs (TI-LFA scenario)

 - inet.0 EBGP unlabeled route followed by LU-IBGP labeled route. 

1) TI-LFA can be disabled

2) Put all labled routes into inet.3: family inet labeled-unicast rib inet.3

3) upgrade to a fixed release PR1818545