1
0
-1
2 answers
- 10-1
From Marco Platania, this resolved the issue:
Brian,
It seems to me that you are using old docker images and/or that the Gerrit branch is not in sync with the dockers. Please modify the heat environment file with the latest docker image version numbers that you can find here: https://gerrit.onap.org/r/gitweb?p=integration.git;a=blob;f=version-manifest/src/main/resources/docker-manifest.csv;h=37cc982c096617932bb8558ab5f7d3230b809369;hb=refs/heads/amsterdam
Robot should use 1.1-STAGING-latest instead.
Also, all the gerrit branches should be “amsterdam” except for message router, which uses master.
Marco
Add your comment... - 10-1
Restacking the environment now with branches set to amsterdam, except mr, and some versions updated.
Add your comment...
When I try to the initiate the APPC mountpoint for the vFW demo I get an error that seems to indicate something is imcomplete or missing from APPCs ODL controller. The APPC deployment with Amsterdam currently doesnt boot by default, it looks for an /opt/appc directory that doesn't exist in the image, but an /opt/sdnc directory does. We've renamed this folder in the container to get it running, maybe this has something to do with it?
URL: http://{{appc_ip}}:8282/restconf/config/network-topology:network-topology/topology/topology-netconf/node/8d1df789-bf7f-4c6a-9515-8f4b7583febd
<errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf">
<error>
<error-type>protocol</error-type>
<error-tag>malformed-message</error-tag>
<error-message>Error parsing input: Unknown child(ren) node(s) detected, identified by: (urn:opendaylight:netconf-node-topology)host, in: list node</error-message>
</error>
</errors>
Also, DROOLS doesnt have an Amsterdam controller? The policy delete, create,and push up to that point works as expected. Also restarting policy in the drools container works as expected.
URL: http://policy.api.simpledemo.onap.org:9696/policy/pdp/engine/controllers/amsterdam/drools
{
"error": "amsterdam not found"
}