Try replacing the /v2 with /v3 in the robot configuration – it probably is keystone.
The other option is to point robot at MultiVIM and let MultiVIM proxy the keystone (it has v2 to v3 proxy capability) Brian From: [email protected] <[email protected]> On Behalf Of [email protected] Sent: Tuesday, June 26, 2018 4:50 AM To: [email protected] Subject: [onap-discuss] Demo.sh init error Okay, so we are running ONAP Amsterdam on Openstack Pike, and trying to execute the demo.sh script. We face the following error. 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 And Models | FAIL | '200 <= 404 < 300' should be true. ------------------------------------------------------------------------------ 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 ============================================================================== Output: /share/logs/demo/InitDemo/output.xml Log: /share/logs/demo/InitDemo/log.html Report: /share/logs/demo/InitDemo/report.html This is pretty common, but we have tried all possible alternatives. In the output.xml, the error occurs at the following point: <msg timestamp="20180626 08:05:47.568" level="TRACE">Arguments: [ 'keystone' | '/v2.0/tokens' | data={'auth': {'passwordCredentials': {'password': 'system', 'username': 'admin'}, 'tenantId': 'ed0cf535cdd44f339bb3f93353885086'}} | headers={'Accept': 'application/json', 'Content-Type': 'application/json', 'X-FromAppId': 'robot-ete', 'X-TransactionId': 'robot-ete-55056fd9-16f5-41f0-8ecf-b5856c25e9f4'} ]</msg> <msg timestamp="20180626 08:05:47.570" level="DEBUG">Starting new HTTP connection (1): 192.168.180.245</msg> <msg timestamp="20180626 08:05:47.576" level="DEBUG">http://192.168.180.245:5000<https://urldefense.proofpoint.com/v2/url?u=http-3A__192.168.180.245-3A5000&d=DwQFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=VfvR7UpNsxaE_O4TQ6RaUmH4xnGDs1x0agzrLTKJBUE&s=UnLfyqbmdcl9G3ymzgmFcugXPKpvS40KH3tVRPoAVRI&e=> "POST /v2.0/tokens HTTP/1.1" 404 136</msg> <msg timestamp="20180626 08:05:47.577" level="DEBUG">post response: {"error": {"message": "(http://192.168.180.245:5000/v2.0/tokens<https://urldefense.proofpoint.com/v2/url?u=http-3A__192.168.180.245-3A5000_v2.0_tokens&d=DwQFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=VfvR7UpNsxaE_O4TQ6RaUmH4xnGDs1x0agzrLTKJBUE&s=6MfeN7txh_lOMoxmQyj_pznmc4P50BjtHsQN4Mqxg_0&e=>): The resource could not be found.", "code": 404, "title": "Not Found"}}</msg> <msg timestamp="20180626 08:05:47.577" level="INFO">Post Request using : alias=keystone, uri=/v2.0/tokens, data={"auth": {"passwordCredentials": {"username": "admin", "password": "system"}, "tenantId": "ed0cf535cdd44f339bb3f93353885086"}}, headers={u'Accept': u'application/json', u'Content-Type': u'application/json', u'X-TransactionId': u'robot-ete-55056fd9-16f5-41f0-8ecf-b5856c25e9f4', u'X-FromAppId': u'robot-ete'}, files=None, allow_redirects=True </msg> <msg timestamp="20180626 08:05:47.577" level="TRACE">Return: <Response [404]></msg> <msg timestamp="20180626 08:05:47.577" level="INFO">${resp} = <Response [404]></msg> <status status="PASS" endtime="20180626 08:05:47.577" starttime="20180626 08:05:47.568"></status> What does this mean? Is there a configuration error with the keystone? We were wondering if its because of the v3 and v2 incompatibility. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10877): https://lists.onap.org/g/onap-discuss/message/10877 Mute This Topic: https://lists.onap.org/mt/22683034/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
