contrail-control crash : IFMapServer::ClientRegister (this=0x7ffcd2a1a4e0, client=0x7f83c34cb570) at controller/src/ifmap/ifmap_server.cc:229

[manishkn]

This crash is seen on a scaled test-bed with 64k VN and 64k LIF

Version : 3.1.3.0-77 mitaka

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/contrail-control'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f83c3140bf0 in ?? ()
(gdb) bt
#0 0x00007f83c3140bf0 in ?? ()
#1 0x000000000049cf7f in IFMapServer::ClientRegister (this=0x7ffcd2a1a4e0, client=0x7f83c34cb570) at controller/src/ifmap/ifmap_server.cc:229
#2 0x000000000049da0d in IFMapServer::ProcessClientWork (this=0x7ffcd2a1a4e0, add=add@entry=true, client=0x7f83c34cb570) at controller/src/ifmap/ifmap_server.cc:267
#3 0x00000000004c65e2 in IFMapXmppChannel::ProcessVrSubscribe (this=0x7f83713bd100, identifier=...) at controller/src/ifmap/ifmap_xmpp.cc:208
#4 0x00000000004d408d in ChannelEventProcTask::Run (this=<optimized out>) at controller/src/ifmap/ifmap_xmpp.cc:72
#5 0x00000000006abed7 in TaskImpl::execute (this=0x7f858d0c3440) at controller/src/base/task.cc:264
#6 0x00007f859468ab3a in ?? () from /usr/lib/libtbb.so.2
#7 0x00007f8594686816 in ?? () from /usr/lib/libtbb.so.2
#8 0x00007f8594685f4b in ?? () from /usr/lib/libtbb.so.2
#9 0x00007f85946820ff in ?? () from /usr/lib/libtbb.so.2
#10 0x00007f85946822f9 in ?? () from /usr/lib/libtbb.so.2
#11 0x00007f85948a6184 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#12 0x00007f859397737d in clone () from /lib/x86_64-linux-gnu/libc.so.6
(gdb)

host1 ='root@10.87.121.77'
host2 ='root@10.87.121.78'
host3 ='root@10.87.121.79'
host4 ='root@10.87.121.80'
host5 ='root@10.87.121.81'
host6 ='root@10.87.121.82'
host7 ='root@10.87.121.83'
host8 ='root@10.87.121.84'
host9 ='root@10.87.121.85'
host10 ='root@10.87.121.86'

host11 ='root@10.87.121.70'
host12 ='root@10.87.121.71'
host13 ='root@10.87.121.72'
host14 ='root@10.87.121.73'
host15 ='root@10.87.121.74'
host16 ='root@10.87.121.75'
host17 ='root@10.87.121.76'

env.roledefs = {
    'all': [host1,host2,host3,host4,host5,host6,host7,host8,host9,host10,host11,host12,host13,host14,host15,host16,host17],
    'cfgm': [host1,host4,host7],
    'openstack': [host10],
    'webui': [host1,host4,host7],
    'control': [host1,host4,host7],
    'compute': [host11,host12,host13,host14,host15,host16,host17],
    'tsn': [host11,host12,host13,host14],
    'toragent': [host11,host12,host13,host14],
    'collector': [host2,host5,host8],
    'database': [host3,host6,host9],
    'build': [host_build],
}

core and bin is stored in /auto/cores/

[vivekananda shenoy (vshenoy83)]

Hi Ananth,

This issue is blocking the NTTC GA drop. So we need to get this fixed ASAP.

Regards,
Vivek

[vivekananda shenoy (vshenoy83)]

This bug along with https://bugs.launchpad.net/juniperopenstack/+bug/1701740.

[Ananth Suryanarayana (anantha-l)]

Standard procedure is to store cores and logs under /cs-shared/bugs/<bug-id>/.
I don't know from where I can access /auto/cores/. It is not mounted in e.g. ubuntu-build02 server.

[Ananth Suryanarayana (anantha-l)]

This is duplicate of https://bugs.launchpad.net/juniperopenstack/+bug/1646407
There is no state in this bug to mark it as such...