Hi Michael,
Mohan, > > Hi, pending state for your kubernetes system means that your server is > not reachable from your host (same machine in this case) > > If you don’t wish to extend your system into a clustered system you > should be able to use the 172.xxx ip for host registration. > > The script inserts a record for the hostname into your /etc/hosts and > by default uses this to register rancher/kubernetes. > > > > Went through your paste – your issue may be the choice of hostname – try > something different without underscores and capitals > > > INFO: ENV: CATTLE_URL=http://Public_IP:8880/v1 > > INFO: ENV: DETECTED_CATTLE_AGENT_IP=Public_IP > The Public_IP address is my VM public IP address. I just replaced 10.xx.xx.xx to Public_IP for security reason. > > > You may docker delete and docker rm your server/client container and rerun > the oom rancher install with a real/routable IP as well. > > Or go into the admin section of rancher and change the server IP/host > > > > Also I am a little suspect of how this script was run – if you ran it as > part of template you would not see your-user > > sudo usermod -aG docker your-user > > > > The ARM template runs entrypoint at the end. I removed it and created VM using ARM template then I am running oom_rancher_setup.sh on the VM using: # ./oom_rancher_setup.sh -b master -s xx.xx.xx.xx -e onap Here is the output of # kubectl describe pod kube-dns-5d7b4487c9-dt6bf --namespace=kube-system http://paste.openstack.org/show/720514/ All the pod shows no nodes available to schedule pods like below. any help? Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedScheduling 4m (x140 over 44m) default-scheduler no nodes available to schedule pods no nodes available to schedule pods > > *From:* [email protected] [mailto:onap-discuss-bounces@ > lists.onap.org] *On Behalf Of *Mohan L > *Sent:* Monday, May 7, 2018 2:09 PM > *To:* [email protected] > *Subject:* [onap-discuss] ONAP installation issue with Azure VM > > > > 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: [email protected] | [email protected] > > IRC: neophy > > Blog : http://lmohanphy.livejournal.com/ > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > you may review at https://www.amdocs.com/about/email-disclaimer >
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
