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"; 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" 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"; 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]<mailto:[email protected]>> on behalf of "Oyebimpe Oparinde via Lists.Onap.Org" <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Tuesday, March 19, 2019 at 10:12 AM To: "FREEMAN, BRIAN D" <[email protected]<mailto:[email protected]>> Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[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<http://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<http://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<http://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<http://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<http://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<http://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]<mailto:[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]<mailto:[email protected]>> Date: 3/19/19 4:35 AM (GMT-05:00) To: "FREEMAN, BRIAN D" <[email protected]<mailto:[email protected]>>, [email protected]<mailto:[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. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16213): https://lists.onap.org/g/onap-discuss/message/16213 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]] -=-=-=-=-=-=-=-=-=-=-=-
