Welcome to the new Linux Foundation Forum!

Cluster:1.13.1 Lab#2.1 Error in Calico Pods

naveenkendyalanaveenkendyala Posts: 1
edited January 31 in LFD259 Class Forum

Hello All:

I am using the latest version of the labs which leverage the 1.13 version of the kubernetes.

Follow the labs, I am seeing the "calico pods" are not running into errors and not starting up:
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
kube-system calico-node-6x5kk 1/2 CrashLoopBackOff 1 58s 192.168.56.102 kworker

Further investigation on logs indicated,
** Readiness probe failed: calico/node is not ready: felix is not ready: Get http://localhost:9099/readiness: dial tcp 127.0.0.1:9099: connect: connection refused Back-off restarting failed container **

Did anyone encounter this error? Appreciate any tips

My Setup: Running two VMs in VirtualBox with Ubuntu 16.04

Thank you
Naveen

Comments

  • serewiczserewicz Posts: 520
    edited January 31

    Hello,

    If you restart the calico pods do they enter running state or continue to have an error?

    When you look at the logs of the calico pods, something like kubectl logs calico-node-6x5kk You can add --previous to see prior instances as well. Are there any messages in the logs that would indicate why they are not running properly?

    As you mention you are using VirtualBox my first thought is the nodes are not able to communicate to each other. Can you ping or SSH and log in from one node to the other? Are all ports open and the interfaces set to allow all traffic?

    Kind regards,

Sign In or Register to comment.