Comment 17 for bug 1768475

The issue was seen again with logging enabled on R5.0-111
I have locked the setup for investigation of logs. Please give it a look. Let me know if any info is required.

Setup details:

Sorry. Correct one are:
nodeg12(10.204.217.52) – Controller + Kube manager
nodeg31(10.204.217.71) - Controller + Kube manager + kube master
nodec58(10.204.217.98) – Controller + Kube manager

nodec60(10.204.217.100) - Compute + k8s Minion
nodec61(10.204.217.101) - Compute + k8s Minion