Closed plirglo closed 2 years ago
I know this is a draft PR. What I have found so far:
allow_mismatch
flag not specified for registry:2.8.0
image (this is what we have in develop)calico
pods not working properly:
kube-system calico-node-5vqcp 0/1 Running 0 65m
kube-system calico-node-l72vd 0/1 Running 0 53m
kube-system calico-node-pvpzm 0/1 Running 0 53m
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 43m default-scheduler Successfully assigned kube-system/calico-node-l72vd to ci-devarmawsalmacalico-kubernetes-node-vm-0
Normal Pulling 43m kubelet Pulling image "ci-devarmawsalmacalico-repository-vm-0:5000/calico/cni:v3.20.3"
Normal Pulled 43m kubelet Successfully pulled image "ci-devarmawsalmacalico-repository-vm-0:5000/calico/cni:v3.20.3" in 1.370066396s
Normal Created 43m kubelet Created container upgrade-ipam
Normal Started 43m kubelet Started container upgrade-ipam
Normal Started 43m kubelet Started container install-cni
Normal Pulling 43m kubelet Pulling image "ci-devarmawsalmacalico-repository-vm-0:5000/calico/cni:v3.20.3"
Normal Pulled 43m kubelet Successfully pulled image "ci-devarmawsalmacalico-repository-vm-0:5000/calico/cni:v3.20.3" in 59.674753ms
Normal Created 43m kubelet Created container install-cni
Normal Pulling 43m kubelet Pulling image "ci-devarmawsalmacalico-repository-vm-0:5000/calico/pod2daemon-flexvol:v3.20.3"
Normal Pulled 43m kubelet Successfully pulled image "ci-devarmawsalmacalico-repository-vm-0:5000/calico/pod2daemon-flexvol:v3.20.3" in 444.5771ms
Normal Created 43m kubelet Created container flexvol-driver
Normal Started 43m kubelet Started container flexvol-driver
Normal Pulling 43m kubelet Pulling image "ci-devarmawsalmacalico-repository-vm-0:5000/calico/node:v3.20.3"
Warning Unhealthy 43m kubelet Readiness probe failed: calico/node is not ready: BIRD is not ready: Failed to stat() nodename file: stat /var/lib/calico/nodename: no such file or directory
Normal Created 43m kubelet Created container calico-node
Normal Started 43m kubelet Started container calico-node
Normal Pulled 43m kubelet Successfully pulled image "ci-devarmawsalmacalico-repository-vm-0:5000/calico/node:v3.20.3" in 1.749567977s
Warning Unhealthy 43m kubelet Readiness probe failed: 2022-06-06 10:02:23.357 [INFO][808] confd/health.go 180: Number of node(s) with BGP peering established = 1
calico/node is not ready: felix is not ready: readiness probe reporting 503
Warning Unhealthy 43m kubelet Readiness probe failed: 2022-06-06 10:02:23.558 [INFO][818] confd/health.go 180: Number of node(s) with BGP peering established = 1
calico/node is not ready: felix is not ready: readiness probe reporting 503
Warning Unhealthy 43m kubelet Readiness probe failed: 2022-06-06 10:02:33.419 [INFO][1862] confd/health.go 180: Number of node(s) with BGP peering established = 2
calico/node is not ready: felix is not ready: readiness probe reporting 503
Warning Unhealthy 43m kubelet Readiness probe failed: 2022-06-06 10:02:43.424 [INFO][2812] confd/health.go 180: Number of node(s) with BGP peering established = 2
calico/node is not ready: felix is not ready: readiness probe reporting 503
Warning Unhealthy 43m kubelet Liveness probe failed: calico/node is not ready: Felix is not live: Get "http://localhost:9099/liveness": dial tcp [::1]:9099: connect: connection refused
Warning Unhealthy 42m kubelet Readiness probe failed: 2022-06-06 10:02:53.379 [INFO][3838] confd/health.go 180: Number of node(s) with BGP peering established = 2
calico/node is not ready: felix is not ready: readiness probe reporting 503
Warning Unhealthy 42m kubelet Readiness probe failed: 2022-06-06 10:03:03.413 [INFO][4889] confd/health.go 180: Number of node(s) with BGP peering established = 2
calico/node is not ready: felix is not ready: readiness probe reporting 503
Warning Unhealthy 42m kubelet Readiness probe failed: 2022-06-06 10:03:13.394 [INFO][5905] confd/health.go 180: Number of node(s) with BGP peering established = 2
calico/node is not ready: felix is not ready: readiness probe reporting 503
Warning Unhealthy 42m kubelet Readiness probe failed: 2022-06-06 10:03:23.447 [INFO][6878] confd/health.go 180: Number of node(s) with BGP peering established = 2
calico/node is not ready: felix is not ready: readiness probe reporting 503
Warning Unhealthy 3m28s (x285 over 42m) kubelet (combined from similar events): Readiness probe failed: 2022-06-06 10:42:23.377 [INFO][225930] confd/health.go 180: Number of node(s) with BGP peering established = 2
calico/node is not ready: felix is not ready: readiness probe reporting 503
canal
deployment failed on TASK [kubernetes_master : Wait for CNI plugin to become ready]
kube-system canal-xt2h4 1/2 Running 0 75m
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning Unhealthy 72s (x493 over 76m) kubelet Readiness probe failed: HTTP probe failed with statuscode: 503
Kudos, SonarCloud Quality Gate passed!
0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells
No Coverage information
0.0% Duplication
/azp run