Re: [onap-discuss] Robot VM Demo.sh is failing to initialize customer
Subhash,
HI, just an observation - you may want to run demo.sh init (as it runs both
./demo.sh init_customer and ./demo.sh distribute) - you may be missing the
models.
See the recommended demo call here
https://wiki.onap.org/display/DW/Tutorial%3A+Creating+a+Service+Instance+from+a+Design+Model#Tutorial:CreatingaServiceInstancefromaDesignModel-RunRobotdemo.shinit
/michael
From: onap-discuss-boun...@lists.onap.org
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Subhash Kumar Singh
Sent: Wednesday, June 28, 2017 11:13
To: Gaurav Gupta (c) <guptagau...@vmware.com>; ROSE, DANIEL V <dr6...@att.com>;
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Robot VM Demo.sh is failing to initialize customer
Hello Everyone,
We made some progress now all the service health-test-cases are passing except
DCAE.
Further, we tried to execute the robot test cases (demo.sh init_customer) to
populate the customers
after updating the keystone_get_auth.template [1] . We Observed that test cases
are passed but we
are not able to see the subscriber in the VID portal.
Please let us know if we are missing some steps in execution of demo script.
Following are the logs from robot execution :
# ./demo.sh init_customer
Starting Xvfb on display :89 with res 1280x1024x24
Executing robot tests at log level TRACE
==
OpenECOMP ETE
==
OpenECOMP ETE.Robot
==
OpenECOMP ETE.Robot.Testsuites
==
OpenECOMP ETE.Robot.Testsuites.Demo :: Executes the VNF Orchestration Test ...
==
Initialize Customer | PASS |
--
OpenECOMP ETE.Robot.Testsuites.Demo :: Executes the VNF Orchestrat... | PASS |
1 critical test, 1 passed, 0 failed
1 test total, 1 passed, 0 failed
==
OpenECOMP ETE.Robot.Testsuites| PASS |
1 critical test, 1 passed, 0 failed
1 test total, 1 passed, 0 failed
==
OpenECOMP ETE.Robot | PASS |
1 critical test, 1 passed, 0 failed
1 test total, 1 passed, 0 failed
==
OpenECOMP ETE | PASS |
1 critical test, 1 passed, 0 failed
1 test total, 1 passed, 0 failed
==
Output: /share/logs/demo/InitCustomer/output.xml
Log: /share/logs/demo/InitCustomer/log.html
Report: /share/logs/demo/InitCustomer/report.html
Additionally, we observed that in robot trace logs that
'cloud-region.cloud-owner' value is set to 'Rackspace'
but we have mentioned {'cloud_env' : 'openstack', .. } in
'/opt/eteshare/config/vm_properties.py' .
Following are the robot trace logs :
Arguments: [ ${data_path}='/aai/v8/business/customers/customer/Demonstration' |
${data}={'global-customer-id': 'Demonstration', 'service-subscriptions':
{'service-subscription': [{'relationship-list': {'relationship':
[{'related-to': 'tenant', 'relationship-data': [{'relationship-key':
'cloud-region.cloud-owner', 'relationship-value': 'Rackspace'},
{'relationship-key': 'cloud-region.cloud-region-id', 'relationship-value':
'RegionOne'}, {'relationship-key': 'tenant.tenant-id', 'relationship-value':
'f1b664a504b34807a39013c0805b0c91'}]}]}, 'service-type': 'vFW'},
{'relationship-list': {'relationship': [{'related-to': 'tenant',
'relationship-data': [{'relationship-key': 'cloud-region.cloud-owner',
'relationship-value': 'Rackspace'}, {'relationship-key':
'cloud-region.cloud-region-id', 'relationship-value': 'RegionOne'},
{'relationship-key': 'tenant.tenant-id', 'relationship-value':
'f1b664a504b34807a39013c0805b0c91'}]}]}, 'service-type': 'vLB'}]},
'subscriber-name': 'Demonstration', 'subscriber-type': 'INFRA'} ]
[1] https://wiki.onap.org/display/DW/Run+demo.sh+on+vanilla+Openstack
--
Regards,
Subhash Kumar Singh
From: Gaurav Gupta (c) [guptagau...@vmware.com]
Sent: Friday, June 16, 2017 21:37
To: ROSE, DANIEL V; Subhash Kumar Singh;
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kanagaraj Manickam
Subject: Re: [onap-discuss] Robot VM Demo.sh is failing to initialize customer
Subhash
These IP Address you will mention in the onap configuration files .
To check which application is holding these ip address .
you can login to eac
Re: [onap-discuss] Robot VM Demo.sh is failing to initialize customer
Hello Everyone,
We made some progress now all the service health-test-cases are passing except
DCAE.
Further, we tried to execute the robot test cases (demo.sh init_customer) to
populate the customers
after updating the keystone_get_auth.template [1] . We Observed that test cases
are passed but we
are not able to see the subscriber in the VID portal.
Please let us know if we are missing some steps in execution of demo script.
Following are the logs from robot execution :
# ./demo.sh init_customer
Starting Xvfb on display :89 with res 1280x1024x24
Executing robot tests at log level TRACE
==
OpenECOMP ETE
==
OpenECOMP ETE.Robot
==
OpenECOMP ETE.Robot.Testsuites
==
OpenECOMP ETE.Robot.Testsuites.Demo :: Executes the VNF Orchestration Test ...
==
Initialize Customer | PASS |
--
OpenECOMP ETE.Robot.Testsuites.Demo :: Executes the VNF Orchestrat... | PASS |
1 critical test, 1 passed, 0 failed
1 test total, 1 passed, 0 failed
==
OpenECOMP ETE.Robot.Testsuites| PASS |
1 critical test, 1 passed, 0 failed
1 test total, 1 passed, 0 failed
==
OpenECOMP ETE.Robot | PASS |
1 critical test, 1 passed, 0 failed
1 test total, 1 passed, 0 failed
==
OpenECOMP ETE | PASS |
1 critical test, 1 passed, 0 failed
1 test total, 1 passed, 0 failed
==
Output: /share/logs/demo/InitCustomer/output.xml
Log: /share/logs/demo/InitCustomer/log.html
Report: /share/logs/demo/InitCustomer/report.html
Additionally, we observed that in robot trace logs that
'cloud-region.cloud-owner' value is set to 'Rackspace'
but we have mentioned {'cloud_env' : 'openstack', .. } in
'/opt/eteshare/config/vm_properties.py' .
Following are the robot trace logs :
Arguments: [ ${data_path}='/aai/v8/business/customers/customer/Demonstration' |
${data}={'global-customer-id': 'Demonstration', 'service-subscriptions':
{'service-subscription': [{'relationship-list': {'relationship':
[{'related-to': 'tenant', 'relationship-data': [{'relationship-key':
'cloud-region.cloud-owner', 'relationship-value': 'Rackspace'},
{'relationship-key': 'cloud-region.cloud-region-id', 'relationship-value':
'RegionOne'}, {'relationship-key': 'tenant.tenant-id', 'relationship-value':
'f1b664a504b34807a39013c0805b0c91'}]}]}, 'service-type': 'vFW'},
{'relationship-list': {'relationship': [{'related-to': 'tenant',
'relationship-data': [{'relationship-key': 'cloud-region.cloud-owner',
'relationship-value': 'Rackspace'}, {'relationship-key':
'cloud-region.cloud-region-id', 'relationship-value': 'RegionOne'},
{'relationship-key': 'tenant.tenant-id', 'relationship-value':
'f1b664a504b34807a39013c0805b0c91'}]}]}, 'service-type': 'vLB'}]},
'subscriber-name': 'Demonstration', 'subscriber-type': 'INFRA'} ]
[1] https://wiki.onap.org/display/DW/Run+demo.sh+on+vanilla+Openstack
--
Regards,
Subhash Kumar Singh
From: Gaurav Gupta (c) [guptagau...@vmware.com]
Sent: Friday, June 16, 2017 21:37
To: ROSE, DANIEL V; Subhash Kumar Singh; onap-discuss@lists.onap.org
Cc: Kanagaraj Manickam
Subject: Re: [onap-discuss] Robot VM Demo.sh is failing to initialize customer
Subhash
These IP Address you will mention in the onap configuration files .
To check which application is holding these ip address .
you can login to each docker container and check netstat -tunlp | grep
ipaddress -- you should see some application running on those ip address and on
specific port .
thanks
Gaurav
From: ROSE, DANIEL V <dr6...@att.com>
Sent: 16 June 2017 21:14
To: Subhash Kumar Singh; Gaurav Gupta (c); onap-discuss@lists.onap.org
Cc: Kanagaraj Manickam
Subject: RE: [onap-discuss] Robot VM Demo.sh is failing to initialize customer
I believe MSO supports keystone 3, so you can use onap except for dcae, but
Robot does not currently support keystone v3 so the demo scripts will not work.
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308
From: Subhash Kumar Singh [mailto:subhash.kumar.si...@huawei.com]
Sent: Friday, June 16, 2017 8:17 AM
To: ROSE, DANIEL V <dr6..
Re: [onap-discuss] Robot VM Demo.sh is failing to initialize customer
Subhash These IP Address you will mention in the onap configuration files . To check which application is holding these ip address . you can login to each docker container and check netstat -tunlp | grep ipaddress -- you should see some application running on those ip address and on specific port . thanks Gaurav From: ROSE, DANIEL V <dr6...@att.com> Sent: 16 June 2017 21:14 To: Subhash Kumar Singh; Gaurav Gupta (c); onap-discuss@lists.onap.org Cc: Kanagaraj Manickam Subject: RE: [onap-discuss] Robot VM Demo.sh is failing to initialize customer I believe MSO supports keystone 3, so you can use onap except for dcae, but Robot does not currently support keystone v3 so the demo scripts will not work. Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308 From: Subhash Kumar Singh [mailto:subhash.kumar.si...@huawei.com] Sent: Friday, June 16, 2017 8:17 AM To: ROSE, DANIEL V <dr6...@att.com>; Gaurav Gupta (c) <guptagau...@vmware.com>; onap-discuss@lists.onap.org Cc: Kanagaraj Manickam <kanagaraj.manic...@huawei.com> Subject: RE: [onap-discuss] Robot VM Demo.sh is failing to initialize customer Hello Daniel and Gaurav, Daniel, Yes, we are using the using keystone 3 (OS_IDENTITY_API_VERSION=3). Could you please let us know, if it is possible to proceed further with keystone v3. Gaurav, Could you please let us know how the DCAE uses these allocated 5 IPs. -- Regards, Subhash Kumar Singh From: ROSE, DANIEL V [dr6...@att.com] Sent: Thursday, June 15, 2017 22:48 To: Gaurav Gupta (c); Subhash Kumar Singh; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: RE: [onap-discuss] Robot VM Demo.sh is failing to initialize customer Also that error means that you are using keystone 3 I believe. Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308 From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gaurav Gupta (c) Sent: Thursday, June 15, 2017 10:50 AM To: Subhash Kumar Singh <subhash.kumar.si...@huawei.com<mailto:subhash.kumar.si...@huawei.com>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: Re: [onap-discuss] Robot VM Demo.sh is failing to initialize customer Subhash Can you try fixing the ete.sh health first . The health check For DCAE fails because the data collection and analytics platform that DCAE controller spins up off the Heat template is not there. Please pull the latest templates from Gerrit (onap_openstack_float.* is the right one). In order for DCAE to work correctly, at this time, you need to manually assign 5 floating IPs to your OpenStack project. This 5 IPs need to be associated to: dcae_coll_float_ip dcae_db_float_ip dcae_hdp1_float_ip dcae_hdp2_float_ip dcae_hdp3_float_ip in whatever order you want. At run time, the DCAE controller will fetch those IPs from the underlying OpenStack platform and assign to the VMs defined above. To assign floating IPs to your project, from the OpenStack horizon dashboard, click on Compute -> Access & Security -> Floating IPs. Then click “Allocate IP To Project” 5 times. OpenStack will assign 5 IPs to you. I will update the wiki page soon https://wiki.onap.org/display/DW/ONAP+Installation+in+Vanilla+OpenStack<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_ONAP-2BInstallation-2Bin-2BVanilla-2BOpenStack=DwMGaQ=uilaK90D4TOVoH58JNXRgQ=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI=sTgGg_7_U5ada56hwhvoUqmrXabov18-uN2trBasJvs=8ZSFZ8NzhjRZqQVQ6hUFSbtAv3zrNu4s6ys6p-TuyKQ=>and send an email when done. Note, however, that DCAE team is still working on a DNS issue within the DCAE collector docker container. The issue is tracked in this Jira: https://jira.onap.org/browse/DCAE-7<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_DCAE-2D7=DwMGaQ=uilaK90D4TOVoH58JNXRgQ=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI=sTgGg_7_U5ada56hwhvoUqmrXabov18-uN2trBasJvs=OX51a2fmXvVRJHuK36u2NwrA3eCXCkJBgzQdqgBk9_E=> Thanks Gaurav From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> <onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>> on behalf of Subhash Kumar Singh <subhash.kumar.si...@huawei.com<mailto:subhash.kumar.si...@huawei.com>> Sent: 15 June 2017 19:50 To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: [onap-discuss] Robot VM Demo.sh is failing to initialize customer Hello Everyone, We are attempting execute 'init_customer' to pre-populate A but we the robot test cases (demo.sh) are failing. At the same time, we can see the healthcheck (ete.sh) is passing after adding some changes to bri
Re: [onap-discuss] Robot VM Demo.sh is failing to initialize customer
I believe MSO supports keystone 3, so you can use onap except for dcae, but Robot does not currently support keystone v3 so the demo scripts will not work. Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308 From: Subhash Kumar Singh [mailto:subhash.kumar.si...@huawei.com] Sent: Friday, June 16, 2017 8:17 AM To: ROSE, DANIEL V <dr6...@att.com>; Gaurav Gupta (c) <guptagau...@vmware.com>; onap-discuss@lists.onap.org Cc: Kanagaraj Manickam <kanagaraj.manic...@huawei.com> Subject: RE: [onap-discuss] Robot VM Demo.sh is failing to initialize customer Hello Daniel and Gaurav, Daniel, Yes, we are using the using keystone 3 (OS_IDENTITY_API_VERSION=3). Could you please let us know, if it is possible to proceed further with keystone v3. Gaurav, Could you please let us know how the DCAE uses these allocated 5 IPs. -- Regards, Subhash Kumar Singh From: ROSE, DANIEL V [dr6...@att.com] Sent: Thursday, June 15, 2017 22:48 To: Gaurav Gupta (c); Subhash Kumar Singh; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: RE: [onap-discuss] Robot VM Demo.sh is failing to initialize customer Also that error means that you are using keystone 3 I believe. Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308 From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gaurav Gupta (c) Sent: Thursday, June 15, 2017 10:50 AM To: Subhash Kumar Singh <subhash.kumar.si...@huawei.com<mailto:subhash.kumar.si...@huawei.com>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: Re: [onap-discuss] Robot VM Demo.sh is failing to initialize customer Subhash Can you try fixing the ete.sh health first . The health check For DCAE fails because the data collection and analytics platform that DCAE controller spins up off the Heat template is not there. Please pull the latest templates from Gerrit (onap_openstack_float.* is the right one). In order for DCAE to work correctly, at this time, you need to manually assign 5 floating IPs to your OpenStack project. This 5 IPs need to be associated to: dcae_coll_float_ip dcae_db_float_ip dcae_hdp1_float_ip dcae_hdp2_float_ip dcae_hdp3_float_ip in whatever order you want. At run time, the DCAE controller will fetch those IPs from the underlying OpenStack platform and assign to the VMs defined above. To assign floating IPs to your project, from the OpenStack horizon dashboard, click on Compute -> Access & Security -> Floating IPs. Then click "Allocate IP To Project" 5 times. OpenStack will assign 5 IPs to you. I will update the wiki page soon https://wiki.onap.org/display/DW/ONAP+Installation+in+Vanilla+OpenStack<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_ONAP-2BInstallation-2Bin-2BVanilla-2BOpenStack=DwMGaQ=uilaK90D4TOVoH58JNXRgQ=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI=sTgGg_7_U5ada56hwhvoUqmrXabov18-uN2trBasJvs=8ZSFZ8NzhjRZqQVQ6hUFSbtAv3zrNu4s6ys6p-TuyKQ=>and send an email when done. Note, however, that DCAE team is still working on a DNS issue within the DCAE collector docker container. The issue is tracked in this Jira: https://jira.onap.org/browse/DCAE-7<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_DCAE-2D7=DwMGaQ=uilaK90D4TOVoH58JNXRgQ=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI=sTgGg_7_U5ada56hwhvoUqmrXabov18-uN2trBasJvs=OX51a2fmXvVRJHuK36u2NwrA3eCXCkJBgzQdqgBk9_E=> Thanks Gaurav From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> <onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>> on behalf of Subhash Kumar Singh <subhash.kumar.si...@huawei.com<mailto:subhash.kumar.si...@huawei.com>> Sent: 15 June 2017 19:50 To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: [onap-discuss] Robot VM Demo.sh is failing to initialize customer Hello Everyone, We are attempting execute 'init_customer' to pre-populate A but we the robot test cases (demo.sh) are failing. At the same time, we can see the healthcheck (ete.sh) is passing after adding some changes to bring up the docker services (https://gerrit.onap.org/r/#/c/5009/<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_5009_=DwMF-g=LFYZ-o9_HUMeMTSQicvjIg=2wwdGZ3YcpSivQ2Kio028A=nK_7CmLjD9kdXAxXtrWN8ABAcK9zsrACqc_sl97MXxc=D0zGvcXY9Pv9ns6GBkIcdn7ff_Y7Uqs5xTN4N-K5km4=>). Following are the logs from robot vm: $ ./demo.sh init_customer Starting Xvfb on display :89 with res 1280x1024x24 Executing robot tests at log level TRACE == OpenECOMP ETE == OpenECO
Re: [onap-discuss] Robot VM Demo.sh is failing to initialize customer
Hello Daniel and Gaurav, Daniel, Yes, we are using the using keystone 3 (OS_IDENTITY_API_VERSION=3). Could you please let us know, if it is possible to proceed further with keystone v3. Gaurav, Could you please let us know how the DCAE uses these allocated 5 IPs. -- Regards, Subhash Kumar Singh From: ROSE, DANIEL V [dr6...@att.com] Sent: Thursday, June 15, 2017 22:48 To: Gaurav Gupta (c); Subhash Kumar Singh; onap-discuss@lists.onap.org Subject: RE: [onap-discuss] Robot VM Demo.sh is failing to initialize customer Also that error means that you are using keystone 3 I believe. Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308 From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gaurav Gupta (c) Sent: Thursday, June 15, 2017 10:50 AM To: Subhash Kumar Singh <subhash.kumar.si...@huawei.com>; onap-discuss@lists.onap.org Subject: Re: [onap-discuss] Robot VM Demo.sh is failing to initialize customer Subhash Can you try fixing the ete.sh health first . The health check For DCAE fails because the data collection and analytics platform that DCAE controller spins up off the Heat template is not there. Please pull the latest templates from Gerrit (onap_openstack_float.* is the right one). In order for DCAE to work correctly, at this time, you need to manually assign 5 floating IPs to your OpenStack project. This 5 IPs need to be associated to: dcae_coll_float_ip dcae_db_float_ip dcae_hdp1_float_ip dcae_hdp2_float_ip dcae_hdp3_float_ip in whatever order you want. At run time, the DCAE controller will fetch those IPs from the underlying OpenStack platform and assign to the VMs defined above. To assign floating IPs to your project, from the OpenStack horizon dashboard, click on Compute -> Access & Security -> Floating IPs. Then click “Allocate IP To Project” 5 times. OpenStack will assign 5 IPs to you. I will update the wiki page soon https://wiki.onap.org/display/DW/ONAP+Installation+in+Vanilla+OpenStack<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_ONAP-2BInstallation-2Bin-2BVanilla-2BOpenStack=DwMGaQ=uilaK90D4TOVoH58JNXRgQ=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI=sTgGg_7_U5ada56hwhvoUqmrXabov18-uN2trBasJvs=8ZSFZ8NzhjRZqQVQ6hUFSbtAv3zrNu4s6ys6p-TuyKQ=>and send an email when done. Note, however, that DCAE team is still working on a DNS issue within the DCAE collector docker container. The issue is tracked in this Jira: https://jira.onap.org/browse/DCAE-7<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_DCAE-2D7=DwMGaQ=uilaK90D4TOVoH58JNXRgQ=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI=sTgGg_7_U5ada56hwhvoUqmrXabov18-uN2trBasJvs=OX51a2fmXvVRJHuK36u2NwrA3eCXCkJBgzQdqgBk9_E=> Thanks Gaurav From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> <onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>> on behalf of Subhash Kumar Singh <subhash.kumar.si...@huawei.com<mailto:subhash.kumar.si...@huawei.com>> Sent: 15 June 2017 19:50 To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: [onap-discuss] Robot VM Demo.sh is failing to initialize customer Hello Everyone, We are attempting execute 'init_customer' to pre-populate A but we the robot test cases (demo.sh) are failing. At the same time, we can see the healthcheck (ete.sh) is passing after adding some changes to bring up the docker services (https://gerrit.onap.org/r/#/c/5009/). Following are the logs from robot vm: $ ./demo.sh init_customer Starting Xvfb on display :89 with res 1280x1024x24 Executing robot tests at log level TRACE == OpenECOMP ETE == OpenECOMP ETE.Robot == OpenECOMP ETE.Robot.Testsuites == OpenECOMP ETE.Robot.Testsuites.Demo :: Executes the VNF Orchestration Test ... == Initialize Customer | FAIL | KeyError: 'tenant' -- OpenECOMP ETE.Robot.Testsuites.Demo :: Executes the VNF Orchestrat... | FAIL | 1 critical test, 0 passed, 1 failed 1 test total, 0 passed, 1 failed == OpenECOMP ETE.Robot.Testsuites| FAIL | 1 critical test, 0 passed, 1 failed 1 test total, 0 passed, 1 failed == OpenECOMP ETE.Ro
Re: [onap-discuss] Robot VM Demo.sh is failing to initialize customer
Also that error means that you are using keystone 3 I believe. Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308 From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gaurav Gupta (c) Sent: Thursday, June 15, 2017 10:50 AM To: Subhash Kumar Singh <subhash.kumar.si...@huawei.com>; onap-discuss@lists.onap.org Subject: Re: [onap-discuss] Robot VM Demo.sh is failing to initialize customer Subhash Can you try fixing the ete.sh health first . The health check For DCAE fails because the data collection and analytics platform that DCAE controller spins up off the Heat template is not there. Please pull the latest templates from Gerrit (onap_openstack_float.* is the right one). In order for DCAE to work correctly, at this time, you need to manually assign 5 floating IPs to your OpenStack project. This 5 IPs need to be associated to: dcae_coll_float_ip dcae_db_float_ip dcae_hdp1_float_ip dcae_hdp2_float_ip dcae_hdp3_float_ip in whatever order you want. At run time, the DCAE controller will fetch those IPs from the underlying OpenStack platform and assign to the VMs defined above. To assign floating IPs to your project, from the OpenStack horizon dashboard, click on Compute -> Access & Security -> Floating IPs. Then click "Allocate IP To Project" 5 times. OpenStack will assign 5 IPs to you. I will update the wiki page soon https://wiki.onap.org/display/DW/ONAP+Installation+in+Vanilla+OpenStack<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_ONAP-2BInstallation-2Bin-2BVanilla-2BOpenStack=DwMGaQ=uilaK90D4TOVoH58JNXRgQ=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI=sTgGg_7_U5ada56hwhvoUqmrXabov18-uN2trBasJvs=8ZSFZ8NzhjRZqQVQ6hUFSbtAv3zrNu4s6ys6p-TuyKQ=>and send an email when done. Note, however, that DCAE team is still working on a DNS issue within the DCAE collector docker container. The issue is tracked in this Jira: https://jira.onap.org/browse/DCAE-7<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_DCAE-2D7=DwMGaQ=uilaK90D4TOVoH58JNXRgQ=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI=sTgGg_7_U5ada56hwhvoUqmrXabov18-uN2trBasJvs=OX51a2fmXvVRJHuK36u2NwrA3eCXCkJBgzQdqgBk9_E=> Thanks Gaurav From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> <onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>> on behalf of Subhash Kumar Singh <subhash.kumar.si...@huawei.com<mailto:subhash.kumar.si...@huawei.com>> Sent: 15 June 2017 19:50 To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: [onap-discuss] Robot VM Demo.sh is failing to initialize customer Hello Everyone, We are attempting execute 'init_customer' to pre-populate A but we the robot test cases (demo.sh) are failing. At the same time, we can see the healthcheck (ete.sh) is passing after adding some changes to bring up the docker services (https://gerrit.onap.org/r/#/c/5009/). Following are the logs from robot vm: $ ./demo.sh init_customer Starting Xvfb on display :89 with res 1280x1024x24 Executing robot tests at log level TRACE == OpenECOMP ETE == OpenECOMP ETE.Robot == OpenECOMP ETE.Robot.Testsuites == OpenECOMP ETE.Robot.Testsuites.Demo :: Executes the VNF Orchestration Test ... == Initialize Customer | FAIL | KeyError: 'tenant' -- OpenECOMP ETE.Robot.Testsuites.Demo :: Executes the VNF Orchestrat... | FAIL | 1 critical test, 0 passed, 1 failed 1 test total, 0 passed, 1 failed == OpenECOMP ETE.Robot.Testsuites| FAIL | 1 critical test, 0 passed, 1 failed 1 test total, 0 passed, 1 failed == OpenECOMP ETE.Robot | FAIL | 1 critical test, 0 passed, 1 failed 1 test total, 0 passed, 1 failed == OpenECOMP ETE | FAIL | 1 critical test, 0 passed, 1 failed 1 test total, 0 passed, 1 failed == $ ./ete.sh health ==
[onap-discuss] Robot VM Demo.sh is failing to initialize customer
Hello Everyone, We are attempting execute 'init_customer' to pre-populate A but we the robot test cases (demo.sh) are failing. At the same time, we can see the healthcheck (ete.sh) is passing after adding some changes to bring up the docker services (https://gerrit.onap.org/r/#/c/5009/). Following are the logs from robot vm: $ ./demo.sh init_customer Starting Xvfb on display :89 with res 1280x1024x24 Executing robot tests at log level TRACE == OpenECOMP ETE == OpenECOMP ETE.Robot == OpenECOMP ETE.Robot.Testsuites == OpenECOMP ETE.Robot.Testsuites.Demo :: Executes the VNF Orchestration Test ... == Initialize Customer | FAIL | KeyError: 'tenant' -- OpenECOMP ETE.Robot.Testsuites.Demo :: Executes the VNF Orchestrat... | FAIL | 1 critical test, 0 passed, 1 failed 1 test total, 0 passed, 1 failed == OpenECOMP ETE.Robot.Testsuites| FAIL | 1 critical test, 0 passed, 1 failed 1 test total, 0 passed, 1 failed == OpenECOMP ETE.Robot | FAIL | 1 critical test, 0 passed, 1 failed 1 test total, 0 passed, 1 failed == OpenECOMP ETE | FAIL | 1 critical test, 0 passed, 1 failed 1 test total, 0 passed, 1 failed == $ ./ete.sh health == OpenECOMP ETE == OpenECOMP ETE.Robot == OpenECOMP ETE.Robot.Testsuites == OpenECOMP ETE.Robot.Testsuites.Health-Check :: Testing ecomp components are... == Basic DCAE Health Check | FAIL | Value of dictionary key 'healthTestStatus' does not match: YELLOW != GREEN -- Basic SDNGC Health Check | PASS | -- Basic A Health Check /var/opt/OpenECOMP_ETE/robot/library/urllib3/connectionpool.py:852: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings InsecureRequestWarning) | PASS | -- Basic Policy Health Check | PASS | -- Basic MSO Health Check| PASS | -- Basic ASDC Health Check | PASS | -- Basic APPC Health Check | PASS | -- Basic Portal Health Check | PASS | -- Basic Message Router Health Check | PASS | -- Basic VID Health Check| PASS | -- OpenECOMP ETE.Robot.Testsuites.Health-Check :: Testing ecomp compo... | FAIL | 10 critical tests, 9 passed, 1 failed 10 tests total, 9 passed, 1 failed == OpenECOMP ETE.Robot.Testsuites| FAIL | 10 critical tests, 9 passed, 1 failed 10 tests total, 9 passed, 1 failed
