You installation scripts didn't run. If you login to the sdnc container and check karag.log you can see if it caught an error or simply didnt get fired.
I've seen this happen with nexus3 or gerrit access problems from your cloud. Brian From: [email protected] [mailto:[email protected]] On Behalf Of Subhash Kumar Singh Sent: Friday, June 23, 2017 10:22 AM To: [email protected] Subject: [onap-discuss] Robot test cases failing for SDNGC Hello Everyone , We are executing the robot test cases (ete.sh health) to check the service health, we are observing that SDNGC is failing the test case because `sdnc_controller_container` is returning response 400. Following are the logs from `robot vm` and `onap-sdnc` vm: Robot test case log: $ sudo ./ete.sh health Starting Xvfb on display :88 with res 1280x1024x24 Executing robot tests at log level TRACE ============================================================================== 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 | FAIL | 400 != 200 ------------------------------------------------------------------------------ Detailed robot log: WORD ${resp} = RequestsLibrary . Post Request sdngc, ${data_path}, data=${data}, headers=${headers} Documentation: Send a POST request on the session object found using the Start / End / Elapsed: 20170623 11:33:24.503 / 20170623 11:33:24.520 / 00:00:00.017 11:33:24.503 TRACE Arguments: [ 'sdngc' | '/restconf/operations/SLI-API:healthcheck' | data=No ne | headers={'Accept': 'application/json', 'Content-Type': 'application/json', 'X-FromAppId': 'robot-ete', 'X-TransactionId': 'robot-ete-60d3c19d-7885-49de-bb7a-f85a5cc789f3'} ] 11:33:24.505 DEBUG Starting new HTTP connection (1): 10.3.0.116 11:33:24.518 DEBUG http://10.3.0.116:8282 "POST /restconf/operations/SLI-API:healthcheck HTTP/1.1" 400 None 11:33:24.520 DEBUG post response: {"errors":{"error":[{"error-type":"protocol","error-tag":"unknown-element","error-message":"The module named 'SLI-API' does not exist."}]}} 11:33:24.520 INFO Post Request using : alias=sdngc, uri=/restconf/operations/SLI-API:healthcheck, data=None, headers={u'Accept': u'application/json', u'Content-Type': u'application/json', u'X-TransactionId': u'robot-ete-60d3c19d-7885-49de-bb7a-f85a5cc789f3', u'X-FromAppId': u'robot-ete'}, files=None, allow_redirects=True 11:33:24.520 TRACE Return: <Response [400]> 11:33:24.520 INFO ${resp} = <Response [400]> Running docker instances in sdnc vm: ubuntu@onap-sdnc:~$ sudo docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 015e896b4e61 openecomp/admportal-sdnc-image:latest "/bin/bash -c 'cd ..." 4 hours ago Up 4 hours 0.0.0.0:8843->8843/tcp sdnc_portal_container 32d06df957b4 openecomp/dgbuilder-sdnc-image:latest "/bin/bash -c 'cd ..." 4 hours ago Up 4 hours 0.0.0.0:3000->3100/tcp sdnc_dgbuilder_container 967fc5a4607e openecomp/sdnc-image:latest "/opt/openecomp/sd..." 4 hours ago Up 4 hours 0.0.0.0:8282->8181/tcp sdnc_controller_container c3195fa2237d mysql/mysql-server:5.6 "/entrypoint.sh my..." 4 hours ago Up 4 hours 0.0.0.0:32768->3306/tcp sdnc_db_container It seems SLI-API module is missing in ODL. Could you please help us to resolve this issue. -- Regards, Subhash Kumar Singh
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
