Hi All, I created a Azure VM with 32vCPU and 128 GB RAM using ARM template attached in OOM-711. I ran oom_rancher_setup.sh script which is attached in OOM-715 and the script execution went well with out any error. But all the pods are pending state for long time.
Here is the complete oom_rancher_setup.sh: http://paste.openstack.org/show/720508/ Any help will be really appreciated. # kubectl get pods --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE kube-system heapster-76b8cd7b5-4xkfg 0/1 Pending 0 1h kube-system kube-dns-5d7b4487c9-dt6bf 0/3 Pending 0 1h kube-system kubernetes-dashboard-f9577fffd-fxtsz 0/1 Pending 0 1h kube-system monitoring-grafana-997796fcf-gzj65 0/1 Pending 0 1h kube-system monitoring-influxdb-56fdcd96b-j5hx7 0/1 Pending 0 1h kube-system tiller-deploy-54bcc55dd5-m6tpg 0/1 Pending 0 1h # kubectl cluster-info Kubernetes master is running at https://Public_IP:8880/r/projects/1a7/kubernetes:6443 Heapster is running at https://Public_IP:8880/r/projects/1a7/kubernetes:6443/api/v1/namespaces/kube-system/services/heapster/proxy KubeDNS is running at https://Public_IP:8880/r/projects/1a7/kubernetes:6443/api/v1/namespaces/kube-system/services/kube-dns/proxy kubernetes-dashboard is running at https://Public_IP:8880/r/projects/1a7/kubernetes:6443/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy monitoring-grafana is running at https://Public_IP:8880/r/projects/1a7/kubernetes:6443/api/v1/namespaces/kube-system/services/monitoring-grafana/proxy monitoring-influxdb is running at https://Public_IP:8880/r/projects/1a7/kubernetes:6443/api/v1/namespaces/kube-system/services/monitoring-influxdb/proxy tiller-deploy is running at https://Public_IP:8880/r/projects/1a7/kubernetes:6443/api/v1/namespaces/kube-system/services/tiller-deploy/proxy -- Thanks & Regards Mobile: 9444955058 E-Mail: l.mohan...@gmail.com | thefossg...@gmail.com IRC: neophy Blog : http://lmohanphy.livejournal.com/
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
