chandralekhapoo
commented
6 years ago hi have you fixed this issue? I too get the same
Open msalmanmasood opened 6 years ago
chandralekhapoo
commented
6 years ago hi have you fixed this issue? I too get the same
Followed all-in-one steps for ubuntu 16.04. all goes smooth until found all contrail service inactive. later manually started all services and the status now is:
for pod_name in
kubectl get pods -n kube-system -o wide | grep ^contrail | awk '{print $1}'; do kubectl exec -it $pod_name -n kube-system -- contrail-status ; done == Contrail Analytics == contrail-collector: initializing (Database:uContrail:Global, KafkaPub connection down) (disabled on boot) contrail-analytics-api: initializing (UvePartitions:UVE-Aggregation[None], Collector, ApiServer connection down) (disabled on boot) contrail-query-engine: timeout (disabled on boot) contrail-alarm-gen: initializing (Collector connection down) (disabled on boot) contrail-snmp-collector: initializing (Collector, ApiServer:SNMP[] connection down) (disabled on boot) contrail-topology: initializing (Collector, ApiServer:Config[] connection down) (disabled on boot) contrail-analytics-nodemgr: initializing (Collector connection down) (disabled on boot) == Contrail Database == contrail-database: inactive (disabled on boot)kafka: active (disabled on boot) contrail-database-nodemgr: initializing (disabled on boot) == Contrail Control == contrail-control: initializing (Number of connections:1, Expected:3 Missing: Collector:Collector,Database:Cassandra) (disabled on boot) contrail-named: active (disabled on boot) contrail-dns: active (disabled on boot) contrail-control-nodemgr: initializing (Collector connection down) (disabled on boot) == Contrail Config == contrail-api: initializing (Collector, Database:Cassandra[] connection down) (disabled on boot) contrail-schema: initializing (Collector, ApiServer:ApiServer[] connection down) (disabled on boot) contrail-svc-monitor: initializing (Collector, Database:Cassandra[] connection down) (disabled on boot) contrail-device-manager: initializing (Collector, ApiServer:ApiServer[] connection down) (disabled on boot) contrail-config-nodemgr: initializing (disabled on boot) == Contrail Config Database== contrail-database: inactive (disabled on boot)
== Contrail Web UI == contrail-webui: active (disabled on boot) contrail-webui-middleware: active (disabled on boot) == Contrail Support Services == zookeeper: inactive
rabbitmq-server: active (disabled on boot) == Contrail Kube Manager == contrail-kube-manager: initializing (Collector, ApiServer:ApiServer[] connection down)
kubectl output:
kubectl get pods -n kube-system -o wide NAME READY STATUS RESTARTS AGE IP NODE contrail-analytics-9mz11 1/1 Running 0 12h 10.101.52.244 ucontrail contrail-analyticsdb-tk2rq 1/1 Running 0 12h 10.101.52.244 ucontrail contrail-controller-zwd0d 1/1 Running 0 12h 10.101.52.244 ucontrail contrail-kube-manager-j7snn 1/1 Running 0 12h 10.101.52.244 ucontrail etcd-ucontrail 1/1 Running 0 12h 10.101.52.244 ucontrail kube-apiserver-ucontrail 1/1 Running 0 12h 10.101.52.244 ucontrail kube-controller-manager-ucontrail 1/1 Running 0 12h 10.101.52.244 ucontrail kube-dns-2425271678-640lh 0/3 Pending 0 12h
kube-proxy-c9979 1/1 Running 0 12h 10.101.52.244 ucontrail
kube-scheduler-ucontrail 1/1 Running 0 12h 10.101.52.244 ucontrail
stack@uContrail:~/contrail-docker$
advice pl!