When installing Contrail 5.1 by using the Contrail Helm deployer, contrail-analytics-snmp pods keep failing while pulling the contrail-topology image, which is not found in registry.
contrail-analytics-snmp
contrail-topology
This article provides the root cause for the failure, and indicates what must be done to resolve the issue.
When a new Contrail 5.1 cluster is installed by using the instructions given in Using Helm Charts to Provision Multinode Contrail OpenStack Ocata with High Availability , the contrail-analytics-snmp pods were seen to continuously fail.
root@c510ctl241:~# kubectl get po -n contrail NAME READY STATUS RESTARTS AGE contrail-analytics-alarm-bmn26 2/2 Running 1 5m contrail-analytics-alarm-bvl79 2/2 Running 1 5m contrail-analytics-alarm-hg29m 2/2 Running 1 5m contrail-analytics-fj5g7 3/3 Running 1 5m contrail-analytics-jmrg7 3/3 Running 1 5m contrail-analytics-snmp-ddpkp 2/3 ImagePullBackOff 1 5m contrail-analytics-snmp-kr8nk 2/3 ImagePullBackOff 1 5m contrail-analytics-snmp-wkn2n 2/3 ImagePullBackOff 1 5m contrail-analytics-vxlpr 3/3 Running 1 5m contrail-analyticsdb-59pdk 2/2 Running 0 5m contrail-analyticsdb-mxv5z 2/2 Running 0 5m contrail-analyticsdb-nodemgr-hm78z 1/1 Running 0 5m contrail-analyticsdb-nodemgr-pjz57 1/1 Running 0 5m contrail-analyticsdb-nodemgr-tps4g 1/1 Running 0 5m contrail-analyticsdb-xpr9z 2/2 Running 0 5m
When the kubectl describe command is executed to get further information, it is reported that the contrail-topology image was not found.
kubectl describe
Normal BackOff 5m (x78 over 23m) kubelet, c510ctl243 Back-off pulling image "hub.juniper.net/contrail/contrail-analytics-topology:5.1.0-0.38" Warning Failed 23s (x101 over 23m) kubelet, c510ctl243 Error: ImagePullBackOff
The reason for the SNMP pods to fail is that the name of the contrail-topology image has been changed from contrail-analytics-topology to contrail-analytics-snmp-topology in Contrail 5.1 and later. Therefore, we need to update it manually for the process to succeed.
contrail-analytics-topology
contrail-analytics-snmp-topology
To resolve the issue, change the image name in contrail-env-images.yaml to contrail_topology: "hub.juniper.net/contrail/contrail-analytics-snmp-topology:5.1.0-0.38" , and then re-create the contrail-analytics chart.
contrail-env-images.yaml
contrail_topology: "hub.juniper.net/contrail/contrail-analytics-snmp-topology:5.1.0-0.38"
contrail-analytics
root@c510ctl241:/opt# kubectl get po -n contrail NAME READY STATUS RESTARTS AGE contrail-analytics-alarm-42n4h 2/2 Running 0 26m contrail-analytics-alarm-c9z9v 2/2 Running 0 26m contrail-analytics-alarm-vnxs6 2/2 Running 0 26m contrail-analytics-l8nj2 3/3 Running 0 26m contrail-analytics-snmp-7t76w 3/3 Running 0 26m contrail-analytics-snmp-kdbfg 3/3 Running 0 26m contrail-analytics-snmp-qlvzn 3/3 Running 0 26m contrail-analytics-tvmsb 3/3 Running 0 26m contrail-analytics-x49fj 3/3 Running 0 26m contrail-analyticsdb-l4x85 2/2 Running 1 2d contrail-analyticsdb-nodemgr-9j52s 1/1 Running 0 2d contrail-analyticsdb-nodemgr-d8vvv 1/1 Running 0 2d contrail-analyticsdb-nodemgr-kgfr7 1/1 Running 0 2d contrail-analyticsdb-x4f66 2/2 Running 0 2d contrail-analyticsdb-x5s98 2/2 Running 0 2d contrail-config-bf2dw 5/5 Running 1 2d contrail-config-vjv7t 5/5 Running 1 2d contrail-config-x9dmw 5/5 Running 1 2d contrail-config-zookeeper-blntp 1/1 Running 0 2d
Observe that the pods are functioning normally now.