calico having issue

sumersingh

Hi,
I follow the lab steps to configure the kubernetes cluster. But calico is not coming UP. Please suggest.

calico-kube-controllers-845589bf5f-cjcrt 1/1 Running 0 54s
calico-node-7bmjp 0/1 Running 0 58s
calico-node-vjzsd 0/1 Running 0 58s

I re-create with updated interface as well not not succeed.

• name: IP_AUTODETECTION_METHOD
  value: "interface=ens5"

2019-12-02 10:15:11.259 [INFO][44] table.go 475: Queueing update of chain. chainName="cali-tw-cali07927fc710b" ipVersion=0x4 table="filter"
2019-12-02 10:15:11.259 [INFO][44] table.go 475: Queueing update of chain. chainName="cali-fw-cali07927fc710b" ipVersion=0x4 table="filter"
2019-12-02 10:15:11.259 [INFO][44] endpoint_mgr.go 524: Updating endpoint routes. id=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"kube-system/coredns-5c98db65d4-8czwq", EndpointId:"eth0"}
2019-12-02 10:15:11.259 [INFO][44] table.go 475: Queueing update of chain. chainName="cali-from-wl-dispatch" ipVersion=0x4 table="filter"
2019-12-02 10:15:11.259 [INFO][44] table.go 475: Queueing update of chain. chainName="cali-to-wl-dispatch" ipVersion=0x4 table="filter"
2019-12-02 10:15:11.259 [INFO][44] endpoint_mgr.go 948: Applying /proc/sys configuration to interface. ifaceName="cali07927fc710b"
2019-12-02 10:15:11.260 [INFO][44] endpoint_mgr.go 948: Applying /proc/sys configuration to interface. ifaceName="cali0958dd21a6e"
2019-12-02 10:15:11.260 [INFO][44] table.go 475: Queueing update of chain. chainName="cali-from-host-endpoint" ipVersion=0x4 table="filter"
2019-12-02 10:15:11.260 [INFO][44] table.go 475: Queueing update of chain. chainName="cali-to-host-endpoint" ipVersion=0x4 table="filter"
2019-12-02 10:15:11.260 [INFO][44] table.go 475: Queueing update of chain. chainName="cali-from-hep-forward" ipVersion=0x4 table="filter"
2019-12-02 10:15:11.260 [INFO][44] table.go 475: Queueing update of chain. chainName="cali-to-hep-forward" ipVersion=0x4 table="filter"
2019-12-02 10:15:11.260 [INFO][44] table.go 475: Queueing update of chain. chainName="cali-from-host-endpoint" ipVersion=0x4 table="mangle"
2019-12-02 10:15:11.260 [INFO][44] table.go 475: Queueing update of chain. chainName="cali-from-host-endpoint" ipVersion=0x4 table="raw"
2019-12-02 10:15:11.260 [INFO][44] table.go 475: Queueing update of chain. chainName="cali-to-host-endpoint" ipVersion=0x4 table="raw"
2019-12-02 10:15:11.260 [INFO][44] endpoint_mgr.go 432: Re-evaluated workload endpoint status adminUp=true failed=false known=true operUp=true status="up" workloadEndpointID=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"kube-system/coredns-5c98db65d4-q72zh", EndpointId:"eth0"}
2019-12-02 10:15:11.261 [INFO][44] status_combiner.go 58: Storing endpoint status update ipVersion=0x4 status="up" workload=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"kube-system/coredns-5c98db65d4-q72zh", EndpointId:"eth0"}
2019-12-02 10:15:11.261 [INFO][44] endpoint_mgr.go 432: Re-evaluated workload endpoint status adminUp=true failed=false known=true operUp=true status="up" workloadEndpointID=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"kube-system/coredns-5c98db65d4-8czwq", EndpointId:"eth0"}
2019-12-02 10:15:11.261 [INFO][44] status_combiner.go 58: Storing endpoint status update ipVersion=0x4 status="up" workload=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"kube-system/coredns-5c98db65d4-8czwq", EndpointId:"eth0"}
2019-12-02 10:15:11.261 [INFO][44] table.go 475: Queueing update of chain. chainName="cali-fip-dnat" ipVersion=0x4 table="nat"
2019-12-02 10:15:11.261 [INFO][44] table.go 475: Queueing update of chain. chainName="cali-fip-snat" ipVersion=0x4 table="nat"
2019-12-02 10:15:11.261 [INFO][44] masq_mgr.go 144: IPAM pools updated, refreshing iptables rule ipVersion=0x4
2019-12-02 10:15:11.261 [INFO][44] table.go 475: Queueing update of chain. chainName="cali-nat-outgoing" ipVersion=0x4 table="nat"
2019-12-02 10:15:11.261 [INFO][44] ipip_mgr.go 222: All-hosts IP set out-of sync, refreshing it.
2019-12-02 10:15:11.261 [INFO][44] ipsets.go 119: Queueing IP set for creation family="inet" setID="all-hosts-net" setType="hash:net"
2019-12-02 10:15:11.263 [INFO][44] ipsets.go 306: Resyncing ipsets with dataplane. family="inet"
2019-12-02 10:15:11.263 [INFO][44] route_table.go 247: Trying to connect to netlink
2019-12-02 10:15:11.276 [INFO][44] ipsets.go 356: Finished resync family="inet" numInconsistenciesFound=0 resyncDuration=2.916678ms
2019-12-02 10:15:11.276 [INFO][44] ipsets.go 749: Doing full IP set rewrite family="inet" numMembersInPendingReplace=1 setID="all-ipam-pools"

chrispokorni

Is this behavior observed before or after updating the Security Group?
Is this during cluster bootstrap or at VM instance restarts?
How is calico started - as root or non-root?

Regards,
-Chris

sumersingh

I have started Calico from root user. Only one container coming up out of 2 for calico pod.

chrispokorni

Is there a specific reason why you chose to start calico as root?
For troubleshooting, it would help if you could provide the actual command you run to start calico, the immediate output produced by it, together with the user/root prompt prefixing the command.

Regards,
-Chris