Seeing "index out of range" error about azure-container-networking HOT 5 CLOSED

@fayizk1 Can you please share the following log files: /var/log/azure-vnet.log and /var/log/azure-vnet-ipam.log

from azure-container-networking.

@fayizk1 Is it still happening with latest CNI? If yes, can you please share above requested two log files? If not, we should close the Issue.

from azure-container-networking.

I encountered the same error with CentOS 7.4, no log files like /var/log/azure-vnet.log or /var/log/azure-vnet-ipam.log on centOS, the error messages from /var/log/messages like below:

Mar 30 16:14:43 localhost systemd: Started libcontainer container a05279f6193142478f5d5ada58c0910820aad32678254535fc484f8ed1116b28.
Mar 30 16:14:43 localhost systemd: Starting libcontainer container a05279f6193142478f5d5ada58c0910820aad32678254535fc484f8ed1116b28.
Mar 30 16:14:43 localhost kernel: SELinux: mount invalid. Same superblock, different security settings for (dev mqueue, type mqueue)
Mar 30 16:14:43 localhost kubelet: 2018/03/30 16:14:43 File not exist /var/run/AzureCNITelemetry.json
Mar 30 16:14:43 localhost kubelet: 2018/03/30 16:14:43 GetReport state file didn't exist. Setting flag to true
Mar 30 16:14:43 localhost kubelet: panic: runtime error: index out of range
Mar 30 16:14:43 localhost kubelet: goroutine 1 [running]:
Mar 30 16:14:43 localhost kubelet: github.com/Azure/azure-container-networking/telemetry.(*Report).GetOSDetails(0xc4200d0640)
Mar 30 16:14:43 localhost kubelet: /go/src/github.com/Azure/azure-container-networking/telemetry/telemetry_linux.go:112 +0x55c
Mar 30 16:14:43 localhost kubelet: github.com/Azure/azure-container-networking/telemetry.(*ReportManager).GetReport(0xc420018340, 0x6ea639, 0x3, 0x70d874, 0x6)
Mar 30 16:14:43 localhost kubelet: /go/src/github.com/Azure/azure-container-networking/telemetry/telemetry.go:138 +0xa3
Mar 30 16:14:43 localhost kubelet: main.main()
Mar 30 16:14:43 localhost kubelet: /go/src/github.com/Azure/azure-container-networking/cni/network/plugin/main.go:65 +0x6e6
Mar 30 16:14:43 localhost kubelet: E0330 16:14:43.982391 65044 cni.go:259] Error adding network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
Mar 30 16:14:43 localhost kubelet: E0330 16:14:43.982411 65044 cni.go:227] Error while adding to cni network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
Mar 30 16:14:43 localhost journal: Shutting down, got signal: Terminated
Mar 30 16:14:44 localhost dockerd-current: time="2018-03-30T16:14:44.035845675Z" level=error msg="containerd: deleting container" error="exit status 1: "container a05279f6193142478f5d5ada58c0910820aad32678254535fc484f8ed1116b28 does not exist\none or more of the container deletions failed\n""

And my network configure file as below:
{
"cniVersion": "0.3.1",
"name": "azure",
"type": "azure-vnet",
"master": "eth0",
"bridge": "azure0",
"logLevel": "info",
"ipam": {
"type": "azure-vnet-ipam",
"environment": "azure"
}
}

I am using the latest version v1.0.3, any idea what's happening? Thanks!

from azure-container-networking.

@fayizk1 We are not getting what's the exact issue. The first log you shared looks completely different from the one you shared now. This is not the same issue. Can you please open a different ticket for this? Also if the first issue gets fixed, Please close this ticket.

from azure-container-networking.

Please open a new issue as suggested by Tamilmani. Closing this one.

from azure-container-networking.