The prepull_docker.sh works and I can see 7 green lines with Kubectl cluster-info. But kubernetes pods just keep pending. Parker would you please help to reinstall a Ubuntu 16.04 in this pod ? Maybe there is no such issue in ubuntu environment.
发件人: Michael O'Brien [mailto:frank.obr...@amdocs.com] 发送时间: 2017年10月18日 4:31 收件人: Tina Tsou <tina.t...@arm.com>; huangxiangyu <huangxiang...@huawei.com>; lylav...@iol.unh.edu; pberber...@iol.unh.edu 抄送: opnfv-tech-disc...@lists.opnfv.org; onap-discuss@lists.onap.org 主题: RE: [Auto] Re: All pods are pending when setting up kubernetes Tina, Harry, It looks like your kubernetes pods under rancher are not up – they are all 0/1 or 0/3 – in the instructions after setting up your kube client run Kubectl cluster-info – you should see all 7 green lines – errors usually means there are issues either with your file system or dns – are you running collocated (server/client on same machine – I think so right?) Also I need to update the meeting minutes with the demo video – I’ll post the time where I checked this during the demo. For any image issues - could you verify that you ran the prepull_docker sh script from the page https://wiki.onap.org/display/DW/ONAP+on+Kubernetes#ONAPonKubernetes-QuickstartInstallation https://jira.onap.org/secure/attachment/10501/prepull_docker.sh [https://jira.onap.org/images/icons/issuetypes/story.svg]OOM-328 - Preload docker images script before createAll.sh will allow 7 min startup IN PROGRESS<https://jira.onap.org/browse/OOM-328> curl https://jira.onap.org/secure/attachment/10501/prepull_docker.sh > prepull_docker.sh chmod 777 prepull_docker.sh nohup ./prepull_docker.sh > prepull.log & Then do the following to verify that at least all the docker images were pulled. Docker images After that try bringing up an independent component like onap-robot – this does not need anything else and can be used to verify your install ./createAll.bash –n onap –a onap-robot /michael From: Tina Tsou [mailto:tina.t...@arm.com] Sent: Tuesday, October 17, 2017 13:21 To: huangxiangyu <huangxiang...@huawei.com<mailto:huangxiang...@huawei.com>>; lylav...@iol.unh.edu<mailto:lylav...@iol.unh.edu>; pberber...@iol.unh.edu<mailto:pberber...@iol.unh.edu> Cc: Michael O'Brien <frank.obr...@amdocs.com<mailto:frank.obr...@amdocs.com>>; opnfv-tech-disc...@lists.opnfv.org<mailto:opnfv-tech-disc...@lists.opnfv.org> Subject: [Auto] Re: All pods are pending when setting up kubernetes Include UNH Lab... Thank you, Tina On Oct 16, 2017, at 11:33 PM, huangxiangyu <huangxiang...@huawei.com<mailto:huangxiang...@huawei.com>> wrote: HI Michael Currently I manage to bring up onap pods in our local lab and most of them are in running state. But there seem to be a rancher bug that block me in UNH lab. Everything seems fine and throws no error when I created rancher-agent. Somehow pods in kube-system just keep getting stuck in pending state. I check the docker images and even images for these pods are not pulled. [root@pod1 ~]# kubectl get pods --all-namespaces -a NAMESPACE NAME READY STATUS RESTARTS AGE kube-system heapster-4285517626-8r16j 0/1 Pending 0 20h kube-system kube-dns-638003847-hkn34 0/3 Pending 0 20h kube-system kubernetes-dashboard-716739405-n7x9l 0/1 Pending 0 20h kube-system monitoring-grafana-2360823841-bfd5b 0/1 Pending 0 1d kube-system monitoring-influxdb-2323019309-mgnb5 0/1 Pending 0 1d kube-system tiller-deploy-737598192-dq0pm 0/1 Pending 0 1d This new pod should be powerful enough but still installed centos. I used to have no problem when setting up undercloud in previous pod which is also a centos pod. Have you ever met this problem ? or maybe we should ask UNH lab to reinstall a Ubuntu OS. Thanks Harry Huang IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. 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 onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
![https://jira.onap.org/images/icons/issuetypes/story.svg]OOM-328](https://jira.onap.org/images/icons/issuetypes/story.svg]OOM-328){kind=link}