BGPaaS: CN crash in BgpPath::PathCompare
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.0 |
Fix Committed
|
High
|
Nischal Sheth | |||
Trunk |
Fix Committed
|
High
|
Nischal Sheth |
Bug Description
3.02 b 41
core is in 10.84.5.
(gdb) bt
#0 BgpPath:
#1 0x00000000005d2d5b in ResolverPath:
#2 0x00000000005d350c in PathResolverPar
at controller/
#3 0x000000000068ee07 in operator() (this=<optimized out>) at /usr/include/
#4 TaskTrigger:
#5 0x0000000000689b3f in TaskImpl::execute (this=0x7fddcfc
#6 0x00007fddd723eb3a in ?? () from /usr/lib/
#7 0x00007fddd723a816 in ?? () from /usr/lib/
#8 0x00007fddd7239f4b in ?? () from /usr/lib/
#9 0x00007fddd72360ff in ?? () from /usr/lib/
#10 0x00007fddd72362f9 in ?? () from /usr/lib/
#11 0x00007fddd745a182 in start_thread (arg=0x7fddaf7f
#12 0x00007fddd652b47d in clone () at ../sysdeps/
crash is seen when a prefix is advertised via BGP (from BGPaaS VM) and via XMPP (AAP/static-route).
In this specific case, prefix on the lo0 interface of the BGPaaS VM was being advertised via BGP and also via XMPP because of AAP config attached to the BGPaaS VMI. In general, the crash could be seen if a prefix has a next-hop that itself has another next-hop.