-
Epic
-
Resolution: Won't Do
-
Highest
-
None
-
None
-
None
-
None
-
DCAEGEN1 Stability fixes for R1
Hi, this is a container for all the issues appearing in R1 that are causing DCAE not to orchestrate properly.
The vFirewall closed-loop use case (the sanity for the release) is not able to run without DCAE (the older version not the gen2 version as it comes in)
Ideally we would not have a gap in functionality between 1.0.0 and 1.1 as R1 comes in.
Update: 20170907: all 19 VMs up (just wait a longer 71 min) and ignore the periodic check on cdapNN
10.0.4.103 zldciad4vicdap00.dcae.simpledemo.openecomp.org cdap00 zldciad4vicdap00 root@263ef3ee2bc5:/opt/app/dcae-controller-platform-server/logs# cat error.log 09/07-21:43:17.627|8261a4a6-d118-48d4-8e8b-8f71e3d0d7c7|??|databus polling|DATABUS_POLLING|263ef3ee2bc5:9998|WARN|1|172.18.0.2|263ef3ee2bc5|||DATABUS-POLLING-FAILED-5001W java.lang.RuntimeException: http error: java.net.UnknownHostException: zldciad4vicoll00.dcae.simpledemo.openecomp.org
- relates to
-
DCAEGEN2-89 2-NIC deployment of DCAE VMs fail
- Closed
-
DCAEGEN2-98 20170709 CDAP00 UnKnownHostException fails to instantiate CDAP DCAE cluster in 1.1
- Closed
-
INT-178 DNS Configuration Error
- Closed
-
DCAEGEN2-67 DCAE CDAP: Collector name not populated in /etc/hosts
- Closed
-
DCAEGEN2-69 DCAE initialisation failure
- Closed
-
DCAEGEN2-71 Running ete.sh on a combination DCAE 1.1.0 on docker 1.0.0-STAGING FAILs with JSONDecodeError
- Closed
-
DCAEGEN2-88 DCAE cdap, stg and collector VMs fail to come up under master:20170828
- Closed
- links to