Subash, DCAE takes longer to install. The DCAE controller spins up 5 additional VMs off the Heat template. This takes about 25 minutes, plus configuration time. Overall, please allow about one hour before running health checks. The VMs may be ready but still getting configured (the Hadoop/CDAP cluster takes the longest).
Regarding point 3) that you mention, those floating IPs will be used by the 5 additional VMs that DCAE controller spins up. If they are not in use, it’s likely that those VMs haven’t been created yet. Thanks, Marco From: <onap-discuss-boun...@lists.onap.org> on behalf of Subhash Kumar Singh <subhash.kumar.si...@huawei.com> Date: Wednesday, June 28, 2017 at 10:50 AM To: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org> Subject: [onap-discuss] DCAE Health-Check is failing Hello Everyone, We are trying run the robot test case (ete.sh) to test the health status of DCAE service but it is failing: # ./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 ------------------------------------------------------------------------------ So, following are the questions that we would like to ask: 1] We observed that in created docker instance (dcaestartupvmcontroller_dcae-controller_1) hosts file is not reflecting correct hostname and IP mapping as provided in the heat template. /etc/hosts : 172.18.0.2 c52bfc0fba28 10.0.4.1 zldcZONESTATEcont00.dcae.simpledemo.openecomp.org cont00 zldcZONESTATEcont00 10.0.4.101 zldcZONESTATEpstg00.dcae.simpledemo.openecomp.org pstg00 zldcZONESTATEpstg00 10.0.4.102 zldcZONESTATEcoll00.dcae.simpledemo.openecomp.org coll00 zldcZONESTATEcoll00 dcae-coll-ZONE.dcae.simpledemo.openecomp.org 10.0.103 zldcZONESTATEcdap00.dcae.simpledemo.openecomp.org cdap00 zldcZONESTATEcdap00 10.0.4.104 zldcZONESTATEcdap01.dcae.simpledemo.openecomp.org cdap01 zldcZONESTATEcdap01 10.0.4.105 zldcZONESTATEcdap02.dcae.simpledemo.openecomp.org cdap02 zldcZONESTATEcdap02 10.0.6.1 policy.api.simpledemo.openecomp.org 2] In the hosts file we are observing one more host entry : 172.18.0.2 c52bfc0fba28 could you please let us know which host/service it is referring, as we are seeing the error message around this IP: /opt/app/dcae-controller-platform-server/logs# tailf error.log 06/28-14:06:17.615|ac864c39-a759-411f-a232-2325b89ade5e|??|databus polling|DATABUS_POLLING||WARN|1|172.18.0.2|c52bfc0fba28|||DCAE-CONTROLLER-DATABUS-POLLING-FAILED-5001W java.lang.RuntimeException: http error: java.net.SocketTimeoutException: connect timed out 3] Could you please let us know the use of five extra assigned IP's to the DCAE, because we are not seeing any process/ docker consuming it. Kindly help us. -- Regards, Subhash Kumar Singh
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
