R4.1-build5: couple of vrouter-agent cores while running sanity

[Sudheendra Rao]

couple of vrouter-agnet cores are seen while running sanity on R4.1 build5 mitaka.

Core 1:
(gdb) bt
#0 0x0000000000eb0cb6 in FlowMgmtTree::OperEntryDelete(FlowMgmtRequest const*, FlowMgmtKey*) ()
#1 0x0000000000eb03e7 in ?? ()
#2 0x0000000000eb076a in FlowMgmtManager::DBRequestHandler(FlowMgmtRequest*, DBEntry const*) ()
#3 0x0000000000eb091c in FlowMgmtManager::DBRequestHandler(boost::shared_ptr<FlowMgmtRequest>) ()
#4 0x0000000000eb7ccc in boost::detail::function::function_obj_invoker1<boost::_bi::bind_t<bool, boost::_mfi::mf1<bool, FlowMgmtManager, boost::shared_ptr<FlowMgmtRequest> >, boost::_bi::list2<boost::_bi::value<FlowMgmtManager*>, boost::arg<1> > >, bool, boost::shared_ptr<FlowMgmtRequest> >::invoke(boost::detail::function::function_buffer&, boost::shared_ptr<FlowMgmtRequest>) ()
#5 0x0000000000ebf13a in QueueTaskRunner<boost::shared_ptr<FlowMgmtRequest>, WorkQueue<boost::shared_ptr<FlowMgmtRequest> > >::RunQueue() ()
#6 0x00000000015e43d7 in TaskImpl::execute() ()
#7 0x00007f7290accb3a in ?? () from /usr/lib/libtbb.so.2
#8 0x00007f7290ac8816 in ?? () from /usr/lib/libtbb.so.2
#9 0x00007f7290ac7f4b in ?? () from /usr/lib/libtbb.so.2
#10 0x00007f7290ac40ff in ?? () from /usr/lib/libtbb.so.2
#11 0x00007f7290ac42f9 in ?? () from /usr/lib/libtbb.so.2
#12 0x00007f7290ce8184 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#13 0x00007f728ffc137d in clone () from /lib/x86_64-linux-gnu/libc.so.6
(gdb)

Core 2: This seems to be same as bug 1730191

(gdb) bt
#0 0x00007fa1625e5c37 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007fa1625e9028 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2 0x00007fa1625debf6 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#3 0x00007fa1625deca2 in __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
#4 0x0000000000fa6a89 in NHKSyncEntry::NHKSyncEntry(NHKSyncObject*, NextHop const*) ()
#5 0x0000000000fa1e2b in MplsKSyncEntry::Sync(DBEntry*) ()
#6 0x00000000010adfb5 in KSyncDBObject::Notify(DBTablePartBase*, DBEntryBase*) ()
#7 0x0000000001491a9a in DBTableBase::RunNotify(DBTablePartBase*, DBEntryBase*) ()
#8 0x0000000001494718 in DBTablePartBase::RunNotify() ()
#9 0x000000000149028e in DBPartition::QueueRunner::Run() ()
#10 0x00000000015e43d7 in TaskImpl::execute() ()
#11 0x00007fa1631b4b3a in ?? () from /usr/lib/libtbb.so.2
#12 0x00007fa1631b0816 in ?? () from /usr/lib/libtbb.so.2
#13 0x00007fa1631aff4b in ?? () from /usr/lib/libtbb.so.2
#14 0x00007fa1631ac0ff in ?? () from /usr/lib/libtbb.so.2
#15 0x00007fa1631ac2f9 in ?? () from /usr/lib/libtbb.so.2
#16 0x00007fa1633d0184 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#17 0x00007fa1626a937d in clone () from /lib/x86_64-linux-gnu/libc.so.6
(gdb)

The cores are copied to location:
/cs-shared/bugs/<buig-id>

[Sudheendra Rao (sudheendra-k)]

[sudheendra@nodem4 1734675]$ pwd
/cs-shared/bugs/1734675
[sudheendra@nodem4 1734675]$ ls
core.contrail-vroute.12792.nodem9.1511780135 core.contrail-vroute.40019.nodem8.1511780124
[sudheendra@nodem4 1734675]$

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/37931
Submitter: Naveen N (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/37932
Submitter: Naveen N (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/37932
Committed: http://github.com/Juniper/contrail-controller/commit/6ef1bb3915cbc10cd743ef56d7f35e1a5bcd358a
Submitter: Zuul (<email address hidden>)
Branch: master

commit 6ef1bb3915cbc10cd743ef56d7f35e1a5bcd358a
Author: Naveen N <email address hidden>
Date: Tue Nov 28 21:42:02 2017 +0530

* Rebake multicast label upon encap change

Ingress replication and edge replication label were not updated
new composite NH with correct encap, resulting in MPLS label pointing
to nexthop which could be deleted or delete marked.
Correcting the same, since we use multicast path, label would rebaked
with nexthop upon path changes. Test case for same.

Change-Id: I03cc8512a419c1c139044a7b3adae63529c976a6
Closes-bug: #1734675

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/37931
Committed: http://github.com/Juniper/contrail-controller/commit/fed19b5bd499e6e317b4a1085e6197067d2a81c7
Submitter: Zuul (<email address hidden>)
Branch: R4.1

commit fed19b5bd499e6e317b4a1085e6197067d2a81c7
Author: Naveen N <email address hidden>
Date: Tue Nov 28 21:42:02 2017 +0530

* Rebake multicast label upon encap change

Ingress replication and edge replication label were not updated
new composite NH with correct encap, resulting in MPLS label pointing
to nexthop which could be deleted or delete marked.
Correcting the same, since we use multicast path, label would rebaked
with nexthop upon path changes. Test case for same.

Change-Id: I03cc8512a419c1c139044a7b3adae63529c976a6
Closes-bug: #1734675