This KB article explains a known issue with respect to etcd post reboots of servers in CSO 5.1.1 HA environment and its possible recovery steps.
Post reboots of servers, etcd pods are in CrashLoopBackOff state. root@startupserver1:/Contrail_Service_Orchestration_5.1.1# kubectl get pods -n infra | grep etcd etcd-etcd-0 1/1 Running 1 73m etcd-etcd-1 0/1 CrashLoopBackOff 9 135m etcd-etcd-2 0/1 CrashLoopBackOff 8 112m
Note : Below are recovery steps needs to be performed in startup server in JTAC presence :
(Note: In order to keep context short, lab snippet of deploy_micro_services has not been provided) etcdkey_infra_sls.tgz