Thanks for your response. Now I have the portal app working fine and I can access the portal again. I increased the liveliness probe to 600 seconds but still got the same error. So I simply uninstalled the dev release and deployed the demo release as described here. https://wiki.onap.org/display/DW/OOM+Helm+%28un%29Deploy+plugins
I edited the onap/values.yaml and the robot/values.yaml files and ran the make robot; make onap command. and the chart was successfully updated. ubuntu@k8s-1:~/oom/kubernetes$ make robot; make onap [robot] make[1]: Entering directory '/home/ubuntu/oom/kubernetes' Hang tight while we grab the latest from your chart repositories... ...Successfully got an update from the "local" chart repository Update Complete. ⎈Happy Helming!⎈ Saving 1 charts Downloading common from repo http://127.0.0.1:8879 Deleting outdated charts ==> Linting robot [INFO] Chart.yaml: icon is recommended 1 chart(s) linted, no failures Successfully packaged chart and saved it to: /home/ubuntu/oom/kubernetes/dist/packages/robot-3.0.0.tgz make[1]: Leaving directory '/home/ubuntu/oom/kubernetes' [onap] make[1]: Entering directory '/home/ubuntu/oom/kubernetes' Hang tight while we grab the latest from your chart repositories... ...Successfully got an update from the "local" chart repository Update Complete. ⎈Happy Helming!⎈ Saving 30 charts ... ... ==> Linting onap Lint OK 1 chart(s) linted, no failures Successfully packaged chart and saved it to: /home/ubuntu/oom/kubernetes/dist/packages/onap-3.0.0.tgz make[1]: Leaving directory '/home/ubuntu/oom/kubernetes' I ran the demo.sh script and still got the same connection error. :( ubuntu@k8s-1:~/oom/kubernetes/robot$ ./demo-k8s.sh onap init Number of parameters: 2 KEY: init ++ kubectl --namespace onap get pods ++ sed 's/ .*//' ++ grep robot + POD=demo-robot-robot-d87f9b64-2g5zl + ETEHOME=/var/opt/OpenECOMP_ETE ++ kubectl --namespace onap exec demo-robot-robot-d87f9b64-2g5zl -- bash -c 'ls -1q /share/logs/ | wc -l' + export GLOBAL_BUILD_NUMBER=13 + GLOBAL_BUILD_NUMBER=13 ++ printf %04d 13 + OUTPUT_FOLDER=0013_demo_init + DISPLAY_NUM=103 + VARIABLEFILES='-V /share/config/vm_properties.py -V /share/config/integration_robot_properties.py -V /share/config/integration_preload_parameters.py' + kubectl --namespace onap exec demo-robot-robot-d87f9b64-2g5zl -- /var/opt/OpenECOMP_ETE/runTags.sh -V /share/config/vm_properties.py -V /share/config/integration_robot_properties.py -V /share/config/integration_preload_parameters.py -d /share/logs/0013_demo_init -i InitDemo --display 103 Starting Xvfb on display :103 with res 1280x1024x24 Executing robot tests at log level TRACE ============================================================================== Testsuites ============================================================================== Testsuites.Demo :: Executes the VNF Orchestration Test cases including setu... ============================================================================== Initialize Customer And Models | FAIL | ConnectionError: HTTPConnectionPool(host='1.2.3.4', port=5000): Max retries exceeded with url: /v2.0/tokens (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f822b2c3f50>: Failed to establish a new connection: [Errno 101] Network is unreachable',)) ------------------------------------------------------------------------------ Testsuites.Demo :: Executes the VNF Orchestration Test cases inclu... | FAIL | 1 critical test, 0 passed, 1 failed 1 test total, 0 passed, 1 failed ============================================================================== Testsuites | FAIL | 1 critical test, 0 passed, 1 failed 1 test total, 0 passed, 1 failed ============================================================================== Output: /share/logs/0013_demo_init/output.xml Log: /share/logs/0013_demo_init/log.html Report: /share/logs/0013_demo_init/report.html I ran the ./ete-k8s.sh onap health command and noticed 49 tests passed but Basic DMAAP Data Router and OOF Health Check failed. Could this be the reason for the Connection ERrror. Please help. Thanks 'Bimpe. On Tue, Mar 26, 2019 at 1:40 PM FREEMAN, BRIAN D <[email protected]> wrote: > Check the liveness probe and readiness probe initial delay for portal db. > We use the public cloud override to increase it for slow environments to > 450 seconds. > > In one particularly bad environment we had to increase it to 900 seconds > to let mariadb install before the config script jobs are attempted. > > > > Brian > > > > > > *From:* Borislav Glozman <[email protected]> > *Sent:* Tuesday, March 26, 2019 8:03 AM > *To:* [email protected]; [email protected] > *Cc:* FREEMAN, BRIAN D <[email protected]>; [email protected] > *Subject:* RE: [onap-discuss] demo-k8s.sh onap init failing > > > > Great, with this cleared, could you please see what portal-app pod > (dev-portal-portal-app-6f57b79969-8qkfc) is stuck waiting for? > > It is probably its readiness init container that waits until another pod > is in Ready state. > > When I run ‘kubectl describe pod’ on my portal-app pod, I get: > > portal-app-job-completion: > > Image: oomk8s/readiness-check:2.0.0 > > Command: > > /root/job_complete.py > > Args: > > --job-name > > aaa-portal-portal-db-config > > > > So I would check whether the portal-portal-db-config job finished > successfully. > > > > Thanks, > > Borislav Glozman > > O:+972.9.776.1988 > > M:+972.52.2835726 > > [image: amdocs-a] > > *Amdocs a **Platinum member of ONAP* > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_open-2Dnetwork_nfv-2Dpowered-2Dby-2Donap&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=V57EsTON-ykJ0CsLYRZ1SCoDpWfwoIfoki6pbBFdBjU&s=98UWd7LgxQzO3wFGYTLMOz37xRpGLyRLFDms7Fky0Dk&e=> > > > > *From:* [email protected] <[email protected]> *On > Behalf Of *Oyebimpe Oparinde > *Sent:* Monday, March 25, 2019 12:00 PM > *To:* [email protected]; Borislav Glozman < > [email protected]> > *Cc:* [email protected]; [email protected] > *Subject:* Re: [onap-discuss] demo-k8s.sh onap init failing > > > > Hi, > > > > This is the output of the helm list. > > > > ubuntu@k8s-1:~/oom/kubernetes$ helm list > NAME REVISION UPDATED > STATUS CHART NAMESPACE > demo 1 Mon Mar 25 09:12:00 2019 > DEPLOYED onap-3.0.0 onap > demo-aaf 1 Mon Mar 25 09:12:01 2019 > DEPLOYED aaf-3.0.0 onap > demo-aai 1 Mon Mar 25 09:12:06 2019 > DEPLOYED aai-3.0.0 onap > demo-appc 1 Mon Mar 25 09:12:16 2019 > DEPLOYED appc-3.0.0 onap > demo-clamp 1 Mon Mar 25 09:12:20 2019 > DEPLOYED clamp-3.0.0 onap > demo-cli 1 Mon Mar 25 09:12:23 2019 > DEPLOYED cli-3.0.0 onap > demo-consul 1 Mon Mar 25 09:12:24 2019 > DEPLOYED consul-3.0.0 onap > demo-contrib 1 Mon Mar 25 09:12:26 2019 > DEPLOYED contrib-3.0.0 onap > demo-dcaegen2 1 Mon Mar 25 09:12:29 2019 > DEPLOYED dcaegen2-3.0.0 onap > demo-dmaap 1 Mon Mar 25 09:12:34 2019 > DEPLOYED dmaap-3.0.0 onap > demo-esr 1 Mon Mar 25 09:12:39 2019 > DEPLOYED esr-3.0.0 onap > demo-log 1 Mon Mar 25 09:12:41 2019 > DEPLOYED log-3.0.0 onap > demo-msb 1 Mon Mar 25 09:12:44 2019 > DEPLOYED msb-3.0.0 onap > demo-multicloud 1 Mon Mar 25 09:12:49 2019 > DEPLOYED multicloud-3.0.0 onap > demo-nbi 1 Mon Mar 25 09:12:56 2019 > DEPLOYED nbi-3.0.0 onap > demo-oof 1 Mon Mar 25 09:12:59 2019 > DEPLOYED oof-3.0.0 onap > demo-policy 1 Mon Mar 25 09:13:09 2019 > DEPLOYED policy-3.0.0 onap > demo-pomba 1 Mon Mar 25 09:13:16 2019 > DEPLOYED pomba-3.0.0 onap > demo-portal 1 Mon Mar 25 09:13:27 2019 > DEPLOYED portal-3.0.0 onap > demo-robot 1 Mon Mar 25 09:13:35 2019 > DEPLOYED robot-3.0.0 onap > demo-sdc 1 Mon Mar 25 09:13:39 2019 > DEPLOYED sdc-3.0.0 onap > demo-sdnc 1 Mon Mar 25 09:13:56 2019 > DEPLOYED sdnc-3.0.0 onap > demo-sniro-emulator 1 Mon Mar 25 09:14:10 2019 > DEPLOYED sniro-emulator-3.0.0 onap > demo-so 1 Mon Mar 25 09:14:13 2019 > DEPLOYED so-3.0.0 onap > demo-uui 1 Mon Mar 25 09:14:23 2019 > DEPLOYED uui-3.0.0 onap > demo-vfc 1 Mon Mar 25 09:14:27 2019 > DEPLOYED vfc-3.0.0 onap > demo-vid 1 Mon Mar 25 09:14:42 2019 > DEPLOYED vid-3.0.0 onap > demo-vnfsdk 1 Mon Mar 25 09:14:49 2019 > DEPLOYED vnfsdk-3.0.0 onap > > > > Thanks > > 'Bimpe. > > > > On Mon, Mar 25, 2019 at 8:58 AM Borislav Glozman < > [email protected]> wrote: > > Please run “helm list” command and send output. > > You may need to delete helm charts repo/cache before redeploying. > > > > Thanks, > > Borislav Glozman > > O:+972.9.776.1988 > > M:+972.52.2835726 > > [image: amdocs-a] > > *Amdocs a **Platinum member of ONAP* > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_open-2Dnetwork_nfv-2Dpowered-2Dby-2Donap&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=V57EsTON-ykJ0CsLYRZ1SCoDpWfwoIfoki6pbBFdBjU&s=98UWd7LgxQzO3wFGYTLMOz37xRpGLyRLFDms7Fky0Dk&e=> > > > > *From:* [email protected] <[email protected]> *On > Behalf Of *Oyebimpe Oparinde > *Sent:* Monday, March 25, 2019 8:17 AM > *To:* Borislav Glozman <[email protected]> > *Cc:* [email protected]; [email protected]; > [email protected] > *Subject:* Re: [onap-discuss] demo-k8s.sh onap init failing > > > > Thanks a lot for your response. > > > > I deleted and redeployed the ONAP C release again following the steps > here > > > https://docs.onap.org/en/casablanca/submodules/oom.git/docs/oom_quickstart_guide.html > <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.onap.org_en_casablanca_submodules_oom.git_docs_oom-5Fquickstart-5Fguide.html&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=V57EsTON-ykJ0CsLYRZ1SCoDpWfwoIfoki6pbBFdBjU&s=8n_Eiz44tA9ItBeNN_dAdFY7PJoIQ0aaakzAlXANzYI&e=> > > and this time, I realised the portal-app pod failed to run and several > other pods which means I cannot access the portal now. > > > > I deleted the pods severally hoping to heal but i still got the same error. > > > > Please how do I make the failing pods run apart from deleting them (which > didnt work). > > > > ubuntu@k8s-1:~$ kubectl get pod -n onap | grep CrashLoopBackOff > dev-appc-appc-ansible-server-76fcf9454d-6g27n 0/1 > CrashLoopBackOff 137 12h > dev-dmaap-dmaap-dr-prov-5969bbf9fb-mpd74 0/1 > CrashLoopBackOff 150 12h > dev-sdnc-sdnc-ansible-server-64bbf769d7-tdwss 0/1 > CrashLoopBackOff 140 12h > ubuntu@k8s-1:~$ kubectl get pod -n onap | grep Error > dev-contrib-netbox-app-provisioning-gwfbs 0/1 > Error 0 12h > dev-sdc-sdc-be-config-backend-5k2hc 0/1 > Init:Error 0 12h > dev-sdc-sdc-dcae-be-tools-4f84b 0/1 > Init:Error 0 12h > dev-sdc-sdc-dcae-be-tools-9pr5r 0/1 > Init:Error 0 12h > dev-sdc-sdc-dcae-be-tools-gmlbg 0/1 > Init:Error 0 12h > dev-sdc-sdc-onboarding-be-cassandra-init-dlftq 0/1 > Init:Error 0 12h > dev-sdc-sdc-wfd-be-workflow-init-8kshp 0/1 > Init:Error 0 12h > dev-vnfsdk-vnfsdk-init-postgres-vrwmm 0/1 > Init:Error 0 12h > > > > ubuntu@k8s-1:~$ kubectl get pod -n onap | grep Init:0/1 > dev-dmaap-dmaap-dr-node-55bbd85686-l249s 0/1 > Init:0/1 79 12h > > dev-portal-portal-app-6f57b79969-8qkfc 0/2 > Init:0/1 38 6h > > > > > > Thanks > > 'Bimpe. > > > > On Sun, Mar 24, 2019 at 4:53 PM Borislav Glozman < > [email protected]> wrote: > > Hi, > > > > I had a similar problem. > > It was because I built master branch before Casablanca. > > My robot chart was from master branch (helm release 4.0.0) > > Please run helm list and make sure your charts are all 3.0.0 for > Casablanca deployment. > > > > Thanks, > > Borislav Glozman > > O:+972.9.776.1988 > > M:+972.52.2835726 > > [image: amdocs-a] > > *Amdocs a **Platinum member of ONAP* > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_open-2Dnetwork_nfv-2Dpowered-2Dby-2Donap&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=V57EsTON-ykJ0CsLYRZ1SCoDpWfwoIfoki6pbBFdBjU&s=98UWd7LgxQzO3wFGYTLMOz37xRpGLyRLFDms7Fky0Dk&e=> > > > > *From:* [email protected] <[email protected]> *On > Behalf Of *Brian > *Sent:* Friday, March 22, 2019 2:46 PM > *To:* Oyebimpe Oparinde <[email protected]> > *Cc:* [email protected]; [email protected] > *Subject:* Re: [onap-discuss] demo-k8s.sh onap init failing > > > > Looks like the robot container isnt up completely or something. > > > > ++ kubectl --namespace onap exec dev-robot-d474f544c-sjr78 > dev-robot-robot-646785574-2stg7 -- bash -c 'ls -1q /share/logs/ | wc -l' > command terminated with exit code 126 > > > > Can you kubectl exec into the robot container ? > > > > kubectl --namespace onap exec -it dev-robot-d474f544c-sjr78 > dev-robot-robot-646785574-2stg7 bash > > > > That line in demo-k8s.sh is running an ‘ls -1q” on the /share/logs > directory to generate the sequence number for a log file so it seems more > like the container isnt up or something. > > > > Brian > > > > > > > > > > *From:* Oyebimpe Oparinde <[email protected]> > *Sent:* Friday, March 22, 2019 1:06 AM > *To:* FREEMAN, BRIAN D <[email protected]> > *Cc:* [email protected]; [email protected] > *Subject:* Re: [onap-discuss] demo-k8s.sh onap init failing > > > > Thanks a lot. > > > > So i undeployed the C Release and deployed again following the steps in > https://docs.onap.org/en/casablanca/submodules/oom.git/docs/oom_quickstart_guide.html > <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.onap.org_en_casablanca_submodules_oom.git_docs_oom-5Fquickstart-5Fguide.html&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=CxE_nxBqOu6ezrHiRQ-Zfyox087OHpXrbsqJncluxVw&s=cxigznLXqEFaJkhlLqt3XHvz6OUpR1EUr2JomNi0qxU&e=> > > > > i ran the demo.sh init command again and this is the error i got. > > > > ubuntu@k8s-1:~/oom/kubernetes/robot$ ./demo-k8s.sh onap init > Number of parameters: > 2 > KEY: > init > ++ kubectl --namespace onap get pods > ++ sed 's/ .*//' > ++ grep robot > + POD='dev-robot-d474f544c-sjr78 > dev-robot-robot-646785574-2stg7' > + ETEHOME=/var/opt/OpenECOMP_ETE > ++ kubectl --namespace onap exec dev-robot-d474f544c-sjr78 > dev-robot-robot-646785574-2stg7 -- bash -c 'ls -1q /share/logs/ | wc -l' > command terminated with exit code 126 > + export 'GLOBAL_BUILD_NUMBER=rpc error: code = 2 desc = oci runtime > error: exec failed: container_linux.go:247: starting container process > caused "exec: \"dev-robot-robot-646785574-2stg7\": executable file not > found in $PATH" > ' > + GLOBAL_BUILD_NUMBER='rpc error: code = 2 desc = oci runtime error: exec > failed: container_linux.go:247: starting container process caused "exec: > \"dev-robot-robot-646785574-2stg7\": executable file not found in $PATH" > '... > > > > Any clue to this problem? > > please help, > > > > Thanks, > > Bimpe. > > > > On Tue, Mar 19, 2019 at 3:41 PM FREEMAN, BRIAN D <[email protected]> wrote: > > You dont need to modify /etc/hosts on the robot server unless you are > having a dns issue. > > Simply put the ip for the keystone server into the appropriate variable in > values.yaml or integration-override.yaml > > > > The robot section of integration-override.yaml should look something like > this (Dublin). > > > > robot: > > enabled: true > > flavor: large > > appcUsername: "WWWW " > > appcPassword: "XXXXXXXXX" > > openStackKeyStoneUrl: "http://10.12.25.2:5000 > <https://urldefense.proofpoint.com/v2/url?u=http-3A__10.12.25.2-3A5000&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=CxE_nxBqOu6ezrHiRQ-Zfyox087OHpXrbsqJncluxVw&s=GKnwMYIdp-hOZea5eq5X2ldfLLMZv7o5XHbSyv8kFFc&e=> > " > > openStackPublicNetId: "971040b2-7059-49dc-b220-4fab50cb2ad4" > > openStackTenantId: "41d6d38489bd40b09ea8a6b6b852dcbd" > > openStackUserName: "XXXXX" > > ubuntu14Image: "ubuntu-14-04-cloud-amd64" > > ubuntu16Image: "ubuntu-16-04-cloud-amd64" > > openStackPrivateNetId: "a92eabce-986a-49f3-bb1b-3b555b6b72f1" > > openStackPrivateSubnetId: "19d93c41-1ab0-490a-b54b-63748ed9d2ce" > > openStackPrivateNetCidr: "10.0.0.0/16 > <https://urldefense.proofpoint.com/v2/url?u=http-3A__10.0.0.0_16&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=CxE_nxBqOu6ezrHiRQ-Zfyox087OHpXrbsqJncluxVw&s=vS6lIBtR1rx07wEKyc_mwC0t09N_eCuQFCo64-FOj7U&e=> > " > > openStackSecurityGroup: "af234ffb-1510-4c92-b6c0-453a22d976b5" > > openStackOamNetworkCidrPrefix: "10.0" > > dcaeCollectorIp: "10.12.5.111" > > vnfPubKey: "ssh-rsa > AAAAB3NzaC1yc2EAAAADAQABAAABAQDKXDgoo3+WOqcUG8/5uUbk81+yczgwC4Y8ywTmuQqbNxlY1oQ0YxdMUqUnhitSXs5S/yRuAVOYHwGg2mCs20oAINrP+mxBI544AMIb9itPjCtgqtE2EWo6MmnFGbHB4Sx3XioE7F4VPsh7japsIwzOjbrQe+Mua1TGQ5d4nfEOQaaglXLLPFfuc7WbhbJbK6Q7rHqZfRcOwAMXgDoBqlyqKeiKwnumddo2RyNT8ljYmvB6buz7KnMinzo7qB0uktVT05FH9Rg0CTWH5norlG5qXgP2aukL0gk1ph8iAt7uYLf1ktp+LJI2gaF6L0/qli9EmVCSLr1uJ38Q8CBflhkh" > > demoArtifactsVersion: "1.3.0" > > demoArtifactsRepoUrl: " > https://nexus.onap.org/content/repositories/releases > <https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.onap.org_content_repositories_releases&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=CxE_nxBqOu6ezrHiRQ-Zfyox087OHpXrbsqJncluxVw&s=H2aC3TWSxUupSrQv732MPSQeK3w4ejYzJv9BHVbi-gc&e=> > " > > scriptVersion: "1.3.0" > > rancherIpAddress: "10.12.5.137" > > config: > > openStackEncryptedPasswordHere: "bbaefXXXXXXXXXXXXXXXXX7dbb9" > > *From:* [email protected] <[email protected]> *On > Behalf Of *kranthi guttikonda > *Sent:* Tuesday, March 19, 2019 10:32 AM > *To:* [email protected]; [email protected]; FREEMAN, > BRIAN D <[email protected]> > *Subject:* Re: [onap-discuss] demo-k8s.sh onap init failing > > > > Do you have connectivity to keystone ip? > > > > Login to robot container and try to ping. > > > > You have to update robot deployment by modifying > templates/demployment.yaml (I am thinking to give this enhancement) > > > > For an example in pod.spec update like below > > > > hostAliases: > > - ip: "1.2.3.4" > > hostnames: > > - "novncproxy.openstack.svc.cluster.local" > > - "keystone.openstack.svc.cluster.local" > > - "nova.openstack.svc.cluster.local" > > - "neutron.openstack.svc.cluster.local" > > - "glance.openstack.svc.cluster.local" > > - "cinder.openstack.svc.cluster.local" > > - "heat.openstack.svc.cluster.local" > > > > This will add entries to robot /etc/hosts file automatically or you need > to adjust your upstream DNS servers to resolve these but again your > kube-dns or Coredns must be configured to use upstream DNS servers. > > > > Make robot and onap > > > > Redeploy. > > > > Thanks, > Kranthi > > > > *From: *<[email protected]> on behalf of "Oyebimpe Oparinde via > Lists.Onap.Org > <https://urldefense.proofpoint.com/v2/url?u=http-3A__Lists.Onap.Org&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=CxE_nxBqOu6ezrHiRQ-Zfyox087OHpXrbsqJncluxVw&s=figBTks8MRUaVs2L8oVfxI04wKB32inxD45fE8IMkTw&e=>" > <[email protected]> > *Reply-To: *"[email protected]" <[email protected]>, " > [email protected]" <[email protected]> > *Date: *Tuesday, March 19, 2019 at 10:12 AM > *To: *"FREEMAN, BRIAN D" <[email protected]> > *Cc: *"[email protected]" <[email protected]> > *Subject: *Re: [onap-discuss] demo-k8s.sh onap init failing > > > > Thanks for your response. > > > > I ran the make robot; make onap command and I got this error :( > > > > > > ubuntu@k8s-1:~/oom/kubernetes$ make robot; make onap > > > > [robot] > > make[1]: Entering directory '/home/ubuntu/oom/kubernetes' > > Hang tight while we grab the latest from your chart repositories... > > ...Unable to get an update from the "local" chart repository ( > http://127.0.0.1:8879): > > Get http://127.0.0.1:8879/index.yaml: dial tcp 127.0.0.1:8879: connect: > connection refused > > Update Complete. ⎈Happy Helming!⎈ > > Saving 1 charts > > Downloading common from repo http://127.0.0.1:8879 > > Save error occurred: could not download > http://127.0.0.1:8879/charts/common-3.0.0.tgz: Get > http://127.0.0.1:8879/charts/common-3.0.0.tgz: dial tcp 127.0.0.1:8879: > connect: connection refused > > Deleting newly downloaded charts, restoring pre-update state > > Error: could not download http://127.0.0.1:8879/charts/common-3.0.0.tgz: > Get http://127.0.0.1:8879/charts/common-3.0.0.tgz: dial tcp 127.0.0.1:8879: > connect: connection refused > > Makefile:42: recipe for target 'dep-robot' failed > > make[1]: *** [dep-robot] Error 1 > > make[1]: Leaving directory '/home/ubuntu/oom/kubernetes' > > Makefile:35: recipe for target 'robot' failed > > make: *** [robot] Error 2 > > > > [onap] > > make[1]: Entering directory '/home/ubuntu/oom/kubernetes' > > Hang tight while we grab the latest from your chart repositories... > > ...Unable to get an update from the "local" chart repository ( > http://127.0.0.1:8879): > > Get http://127.0.0.1:8879/index.yaml: dial tcp 127.0.0.1:8879: connect: > connection refused > > Update Complete. ⎈Happy Helming!⎈ > > Saving 30 charts > > Downloading aaf from repo http://127.0.0.1:8879 > > Save error occurred: could not download > http://127.0.0.1:8879/charts/aaf-3.0.0.tgz: Get > http://127.0.0.1:8879/charts/aaf-3.0.0.tgz: dial tcp 127.0.0.1:8879: > connect: connection refused > > Deleting newly downloaded charts, restoring pre-update state > > Error: could not download http://127.0.0.1:8879/charts/aaf-3.0.0.tgz: Get > http://127.0.0.1:8879/charts/aaf-3.0.0.tgz: dial tcp 127.0.0.1:8879: > connect: connection refused > > Makefile:42: recipe for target 'dep-onap' failed > > make[1]: *** [dep-onap] Error 1 > > make[1]: Leaving directory '/home/ubuntu/oom/kubernetes' > > Makefile:35: recipe for target 'onap' failed > > make: *** [onap] Error 2 > > > > > > Did I miss something? Please help. > > > > Thanks in advance, > > Bimpe. > > > > On Tue, Mar 19, 2019 at 1:38 PM FREEMAN, BRIAN D <[email protected]> wrote: > > Did you run make robot ; make onap ? > > Your robot is still using the default ip > > > > Brian > > > > > > > > Sent via the Samsung Galaxy S8, an AT&T 5G Evolution smartphone > > > > > > -------- Original message -------- > > From: Oyebimpe Oparinde <[email protected]> > > Date: 3/19/19 4:35 AM (GMT-05:00) > > To: "FREEMAN, BRIAN D" <[email protected]>, [email protected] > > Subject: demo-k8s.sh onap init failing > > > > Hi, > > > > I'm trying to implement the vFW use case on ONAP C release. > > > > I ran the ./demo-k8s.sh onap init command but failed with the below error. > > > > btw; I have edited the values.yaml file in the directory > ~/oom/kubernetes/robot/values.yaml > > > > > > > > Number of parameters: > > 2 > > KEY: > > init > > ++ kubectl --namespace onap get pods > > ++ sed 's/ .*//' > > ++ grep robot > > + POD=dev-robot-d474f544c-sjr78 > > + ETEHOME=/var/opt/OpenECOMP_ETE > > ++ kubectl --namespace onap exec dev-robot-d474f544c-sjr78 -- bash -c 'ls > -1q /share/logs/ | wc -l' > > + export GLOBAL_BUILD_NUMBER=31 > > + GLOBAL_BUILD_NUMBER=31 > > ++ printf %04d 31 > > + OUTPUT_FOLDER=0031_demo_init > > + DISPLAY_NUM=121 > > + VARIABLEFILES='-V /share/config/vm_properties.py -V > /share/config/integration_robot_properties.py -V > /share/config/integration_preload_parameters.py' > > + kubectl --namespace onap exec dev-robot-d474f544c-sjr78 -- > /var/opt/OpenECOMP_ETE/runTags.sh -V /share/config/vm_properties.py -V > /share/config/integration_robot_properties.py -V > /share/config/integration_preload_parameters.py -d > /share/logs/0031_demo_init -i InitDemo --display 121 > > Starting Xvfb on display :121 with res 1280x1024x24 > > Executing robot tests at log level TRACE > > > ============================================================================== > > Testsuites > > > > ============================================================================== > > Testsuites.Demo :: Executes the VNF Orchestration Test cases including > setu... > > > ============================================================================== > > Initialize Customer And Models | > FAIL | > > ConnectionError: HTTPConnectionPool(host='1.2.3.4', port=5000): Max > retries exceeded with url: /v2.0/tokens (Caused by > NewConnectionError('<urllib3.connection.HTTPConnection object at > 0x7ff3bd05d890>: Failed to establish a new connection: [Errno 101] > Network is unreachable',)) > > > ------------------------------------------------------------------------------ > > Testsuites.Demo :: Executes the VNF Orchestration Test cases inclu... | > FAIL | > > 1 critical test, 0 passed, 1 failed > > 1 test total, 0 passed, 1 failed > > > ============================================================================== > > Testsuites | > FAIL | > > 1 critical test, 0 passed, 1 failed > > 1 test total, 0 passed, 1 failed > > > ============================================================================== > > Output: /share/logs/0031_demo_init/output.xml > > Log: /share/logs/0031_demo_init/log.html > > Report: /share/logs/0031_demo_init/report.html > > > > > > > > Please help solve the problem. > > > > Kind Regards, > > Bimpe. > > > > *This email and the information contained herein is proprietary and > confidential and subject to the Amdocs Email Terms of Service, which you > may review at* *https://www.amdocs.com/about/email-terms-of-service* > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Dterms-2Dof-2Dservice&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=V57EsTON-ykJ0CsLYRZ1SCoDpWfwoIfoki6pbBFdBjU&s=MN-mXsu1pfUhzzjJngVzIzxW8iCJcAfrosyz_Z-kSvo&e=> > > *This email and the information contained herein is proprietary and > confidential and subject to the Amdocs Email Terms of Service, which you > may review at* *https://www.amdocs.com/about/email-terms-of-service* > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Dterms-2Dof-2Dservice&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=V57EsTON-ykJ0CsLYRZ1SCoDpWfwoIfoki6pbBFdBjU&s=MN-mXsu1pfUhzzjJngVzIzxW8iCJcAfrosyz_Z-kSvo&e=> > > > > *This email and the information contained herein is proprietary and > confidential and subject to the Amdocs Email Terms of Service, which you > may review at* *https://www.amdocs.com/about/email-terms-of-service* > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Dterms-2Dof-2Dservice&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=V57EsTON-ykJ0CsLYRZ1SCoDpWfwoIfoki6pbBFdBjU&s=MN-mXsu1pfUhzzjJngVzIzxW8iCJcAfrosyz_Z-kSvo&e=> > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16332): https://lists.onap.org/g/onap-discuss/message/16332 Mute This Topic: https://lists.onap.org/mt/30506217/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
