[R4.1 - 59] Core observed during k8s sanity run (core.async_5)

[Pulkit Tandon]

R4.1 - 59
Contrail ansible provisioning
K8s HA setup
3 Control nodes
2 Compute nodes

Observed following crashes after sanity run on 1 of the controller node:
'core.async_5.1021.testbed-1-vm4.1512889288', 'core.async_5.1021.testbed-1-vm4.1512889288', 'core.async_5.1021.testbed-1-vm4.1512889288', 'core.async_5.1021.testbed-1-vm4.1512889288

To debug, core files can be found on following log path:
http://10.204.216.50/Docs/logs/4.1.1.0-59_2017_12_10_11_36_32_1512890184.75/logs/

After inspection of core, if there is any other information required, do let me know.

[Pulkit Tandon (pulkitt)]

Crashes observed on build R4.1 - 61 as well.

Core file kept at following path:
<email address hidden>:/home/bhushana/Documents/technical/bugs/1737488

[Jeba Paulaiyan (jebap)]

Hi Jeba

It fails all the alarm test cases in vcenter only sanity
http://10.204.216.50/Docs/logs/4.1.1.0-64_jenkins-ubuntu-16-04_vcenter_only_CB_sanity-294_1513379298.27/junit-noframes.html

Regards
Sandip

[Sachchidanand Vaidya (vaidyasd)]

This is not a contrail component core but related K8S component. In a running k8S system, I don't see any process related to this.
Can you try to reproduce and leave the setup in that state.

[Pulkit Tandon (pulkitt)]

Not seeing this issue on R5.1 trunk branch or R5.0-10 branch.
Hence marking it invalid for this branch