crash (core) file created in contrail at customer site

[dshimo]

Hi Team,

A crashes/core file was created in our customer site compute node.
Customer want to know why this core file is created.
<--- 3 files created
core.contrail-vroute.17893.B-9-BL460C-05.1427082091
core.contrail-vroute.1643.B-9-BL460C-05.1426214768
core.contrail-vroute.2981.B-9-BL460C-05.1426154350

<--- Openstack-status in Compute node
root@B-9-BL460C-05:~# openstack-status
== Nova services ==
openstack-nova-api: inactive (disabled on boot)
openstack-nova-compute: active
openstack-nova-network: inactive (disabled on boot)
openstack-nova-scheduler: inactive (disabled on boot)
openstack-nova-volume: inactive (disabled on boot)
== Support services ==
libvirt-bin: active
Warning novarc not sourced
root@B-9-BL460C-05:~# contrail-status
== Contrail vRouter ==
supervisor-vrouter: active
contrail-vrouter-agent active
contrail-vrouter-nodemgr active

========Run time service failures=============
/var/crashes/core.contrail-vroute.17893.B-9-BL460C-05.1427082091
/var/crashes/core.contrail-vroute.1643.B-9-BL460C-05.1426214768
/var/crashes/core.contrail-vroute.2981.B-9-BL460C-05.1426154350
root@B-9-BL460C-05:~# contrail-status lell /var/crashes/core.contrail-vroute.17893.B-9-BL460C-05.1 427082091
-rw------- 1 root root 280764416 3 23 12:41 /var/crashes/core.contrail-vroute.17893.B-9-BL460C-05.1427082091
root@B-9-BL460C-05:~# ll /var/crashes/core.contrail-vroute.1643.B-9-BL460C-05.14 26214768
-rw------- 1 root root 201338880 3 13 11:46 /var/crashes/core.contrail-vroute.1643.B-9-BL460C-05.1426214768
root@B-9-BL460C-05:~# ll /var/crashes/core.contrail-vroute.2981.B-9-BL460C-05.14 26154350
-rw------- 1 root root 208076800 3 12 18:59 /var/crashes/core.contrail-vroute.2981.B-9-BL460C-05.1426154350
root@B-9-BL460C-05:~# service nova-compu-com

[dshimo (dshimo)]

3 core files upload - in crashes.zip file

[Hari Prasad Killi (haripk)]

Two cores are due to the same problem - VRF delete timeout assert. MPLS label having composite NH (L2 composite) referering to the VRF is not deleted.

Third core is while processing a unicast route delete, while the VRF table seems to have been already deleted.

[Hari Prasad Killi (haripk)]

The latter issue is tracked with https://bugs.launchpad.net/juniperopenstack/+bug/1443401