ECMP route where nexthop pointing to combo of MX,contrail intfs can get wrong encap

[Vedamurthy Joshi]

R2.0 Build 41 Ubuntu 12.04 Multi-node regression setup

Create a public VN 10.204.219.88/29 with RT so that routes with MX are exchanged.
inet vrf of public has route for 0.0.0.0/0 pointing to MX

Create a new VM in public VN (with VMI p1)
Now add a interface static route with prefix 0.0.0.0/0 to point to VMI p1

This results in a ECMP route (one path to MX, another to VMI p1)

Now change the encap from {MPLSoUDP, MPLSoGRE, VXLAN} to {MPLSoGRE, MPLSoUDP, VXLAN} and to {VXLAN, MPLSoUDP, MPLSoGRE}

It was then seen that there were two tunnel nexthops for MX, one with encap MPLSoGRE, and another with encap MPLSoUDP

Per Manish, this is a known behavior in ecmp if the encaps are different.
Note that this bug is different from bug 1427849 ( in this case, ECMP was involving 2 MXs, both having the same encap)

root@nodec54:~# nh --get 19
Id:019 Type:Tunnel Fmly: AF_INET Flags:Valid, MPLSoUDP, Rid:0 Ref_cnt:2
        Oif:0 Len:14 Flags Valid, MPLSoUDP, Data:2c 21 72 a0 4a 80 00 25 90 c5 62 62 08 00
        Vrf:0 Sip:10.204.217.94 Dip:10.204.216.253

root@nodec54:~#

env.roledefs = {
    'all': [host2, host3, host4, host5, host6],
    'cfgm': [host2, host3],
    'openstack': [host2],
    'webui': [host3],
    'control': [host3, host4],
    'compute': [host5, host6],
    'collector': [host2, host3],
    'database': [host2, host3, host4],
    'toragent': [host6],
    'tsn': [host6],
    'build': [host_build],
}

env.hostnames = {
    'all': ['nodei34', 'nodei35', 'nodei36', 'nodei37', 'nodei38']
}