Topics

[SMO installation] pls help to check whether ONAP is deployed successfully

Zhengwei Gao
 

Hi experts,

I am trying the [SMO installation].  I am not sure whether ONAP is successfully deployed, pls help, thanks.

dabs@smobronze:~/oran/dep/smo/bin$ sudo kubectl get pods --all-namespaces

NAMESPACE     NAME                                          READY   STATUS      RESTARTS   AGE

kube-system   coredns-5d4dd4b4db-fdfqd                      1/1     Running     4          23h

kube-system   coredns-5d4dd4b4db-rzn6z                      1/1     Running     4          23h

kube-system   etcd-smobronze                                1/1     Running     5          23h

kube-system   kube-apiserver-smobronze                      1/1     Running     5          23h

kube-system   kube-controller-manager-smobronze             1/1     Running     4          23h

kube-system   kube-flannel-ds-amd64-zv4pj                   1/1     Running     6          23h

kube-system   kube-proxy-vml6p                              1/1     Running     5          23h

kube-system   kube-scheduler-smobronze                      1/1     Running     5          23h

kube-system   tiller-deploy-666f9c57f4-8xjwj                1/1     Running     4          23h

onap          dev-consul-68d576d55c-p84w9                   1/1     Running     0          35m

onap          dev-consul-server-0                           1/1     Running     0          35m

onap          dev-consul-server-1                           1/1     Running     0          35m

onap          dev-consul-server-2                           1/1     Running     0          35m

onap          dev-kube2msb-9fc58c48-8bnbw                   1/1     Running     0          35m

onap          dev-mariadb-galera-0                          1/1     Running     0          35m

onap          dev-mariadb-galera-1                          1/1     Running     0          29m

onap          dev-mariadb-galera-2                          1/1     Running     2          24m

onap          dev-message-router-0                          1/1     Running     0          35m

onap          dev-message-router-kafka-0                    1/1     Running     0          35m

onap          dev-message-router-kafka-1                    1/1     Running     0          35m

onap          dev-message-router-kafka-2                    1/1     Running     0          35m

onap          dev-message-router-zookeeper-0                1/1     Running     0          35m

onap          dev-message-router-zookeeper-1                1/1     Running     0          35m

onap          dev-message-router-zookeeper-2                1/1     Running     0          35m

onap          dev-msb-consul-65b9697c8b-lrg4j               1/1     Running     0          35m

onap          dev-msb-discovery-54b76c4898-4k7gs            2/2     Running     0          35m

onap          dev-msb-eag-76d4b9b9d7-4z9sn                  2/2     Running     0          35m

onap          dev-msb-iag-65c59cb86b-7xs8g                  2/2     Running     0          35m

onap          dev-sdnc-0                                    2/2     Running     0          34m

onap          dev-sdnc-db-0                                 1/1     Running     0          34m

onap          dev-sdnc-dmaap-listener-5c77848759-p9rcf      1/1     Running     0          34m

onap          dev-sdnc-sdnrdb-init-job-nvfj8                0/1     Completed   0          34m

onap          dev-sdnrdb-coordinating-only-9b9956fc-j8n6j   2/2     Running     0          34m

onap          dev-sdnrdb-master-0                           1/1     Running     0          34m

onap          dev-sdnrdb-master-1                           1/1     Running     0          25m

onap          dev-sdnrdb-master-2                           1/1     Running     0          20m


The dev-sdnc-sdnrdb-init-job-nvfj8 pod is not ready but completed.


And the two mariadb pods:dev-mariadb-galera-0 and dev-sdnc-db-0 has following warnings:

dabs@smobronze:~/oran/dep/smo/bin$ sudo kubectl describe pod  dev-mariadb-galera-0 -n onap

Warning  Unhealthy         34m   kubelet, smobronze  Readiness probe failed: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2 "No such file or directory")

 

dabs@smobronze:~/oran/dep/smo/bin$ sudo kubectl describe pod  dev-sdnc-db-0 -n onap

Warning  Unhealthy         34m   kubelet, smobronze  Readiness probe failed: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2 "No such file or directory")


--
br, zhengwei gao