[Build CentOS release 6.5 2.10-37~icehouse.el6] Multi-Interface Sanity - vrouter crashed at NhDecode(NextHop const*, PktInfo const*, PktFlowInfo*, PktControlInfo*, PktControlInfo*, bool)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
Fix Committed
|
High
|
Naveen N | ||
R2.0 |
Fix Committed
|
High
|
Naveen N | ||
R2.1 |
Fix Committed
|
High
|
Naveen N |
Bug Description
Logs saved at :http://
BT
===
#0 0x000000000123fc8c in NextHop::id() const ()
#0 0x000000000123fc8c in NextHop::id() const ()
#1 0x00000000014aaedf in NhDecode(NextHop const*, PktInfo const*, PktFlowInfo*, PktControlInfo*, PktControlInfo*, bool) ()
#2 0x00000000014ab24a in RouteToOutInfo(
#3 0x00000000014ad37f in PktFlowInfo:
#4 0x00000000014adeb8 in PktFlowInfo:
#5 0x00000000014b91e7 in FlowHandler::Run() ()
#6 0x00000000014b511f in Proto::
#7 0x00000000014b7543 in boost::
#8 0x00000000014b6f04 in bool boost::
#9 0x00000000014b67ba in bool boost::
#10 0x00000000014b62a9 in boost::
#11 0x00000000014a9c2f in boost::
#12 0x00000000014b7928 in QueueTaskRunner
#13 0x00000000014b7760 in QueueTaskRunner
#14 0x0000000001a84676 in TaskImpl::execute() ()
#15 0x00002b4ae65b018a in tbb::internal:
child=
at /ecbuilds/
#16 0x00002b4ae65a7033 in tbb::internal:
at /ecbuilds/
#17 0x00002b4ae65a5906 in tbb::internal:
j=...)
at /ecbuilds/
#18 0x00002b4ae65a04bc in tbb::internal:
this=0x41a7200)
at /ecbuilds/
#19 0x00002b4ae65a0362 in tbb::internal:
Changed in juniperopenstack: | |
importance: | Undecided → High |
Though there was only one vgw in setup exporting 0/0 route, agent got a ecmp route for 0/0 route,
thought both next hop and label are same,there encap types differ.
<message from=\"<email address hidden>\" to=\"nodei5/ bgp-peer\ "> jabber. org/protocol/ pubsub\"> 1/1/default- domain: admin:vgwvn: vgwvn\" >
<entry>
< nlri>
<af> 1</af>
<safi> 1</safi>
<address> 0.0.0.0/ 0</address>
< /nlri>
< next-hops>
<next- hop>
<af>1</ af>
<address> 192.168. 192.5</ address>
<label> 17</label>
<tunnel- encapsulation- list>
<tunnel- encapsulation> gre</tunnel- encapsulation>
</tunnel- encapsulation- list>
</next- hop>
<next- hop>
<af>1</ af>
<address> 192.168. 192.5</ address>
<label> 17</label>
<tunnel- encapsulation- list>
<tunnel- encapsulation> gre</tunnel- encapsulation>
<tunnel- encapsulation> udp</tunnel- encapsulation>
</tunnel- encapsulation- list>
</next- hop>
< /next-hops>
< version> 1</version>
< virtual- network> default- domain: admin:vgwvn< /virtual- network>
< sequence- number> 0</sequence- number>
< security- group-list />
< local-preferenc e>100</ local-preferenc e>
</entry>
<event xmlns=\"http://
<items node=\"
<item id=\"0.0.0.0/0\">
</item>
</items>
If there is a ecmp of vgw and traffic originates first from outside to contrail-domain VM,
agent was trying to get policy enabled next hop for reverse flow setup which would not
be created for vgw.
Fix for to take policy enabled next hop for reverse flow only destination is vm interface.