Subhash,
I had the same observation with new "new" HEAT template which uses 2 AAI
VMs. reverting back to the previous HEAT template (with one VM for AAI)
has solved this issue for me.
Btw, running demo.sh init second time creates an error (I believe this is
also discussed in this mailing list in the last week or the week before
the last)
Mit freundlichen Grüßen / Kind regards
Josef Reisinger
From: "Michael O'Brien"
To: Subhash Kumar Singh , "Gaurav
Gupta (c)" , "ROSE, DANIEL V" ,
"onap-discuss@lists.onap.org"
Date: 28.06.2017 17:26
Subject:Re: [onap-discuss] Robot VM Demo.sh is failing to
initialize customer
Sent by:onap-discuss-boun...@lists.onap.org
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) ; ROSE, DANIEL V
; 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': 'v