Gary,
The log of dcae bootstrap docker container shows that there was a transient
problem last night. One of the artifacts hosted by LF Nexus server failed to
download (getting “502 bad gateway” response). I dumped the docker log to
file /opt/log-docker-15afe9c18611-20180110 on the dcae bootstrap VM and line
and line 1515 shows the problem.
So after cleaning up I re-ran the vm_init bash script again. The deployment
has passed the failure point last night.
Now there is another problem. One of DCAE subcomponent failed due to now able
to contact docker registry. I found that the configuration for nexus docker
repo is set to “10.12.5.80:5000”. The error message says expects https but
getting http response: “dockerplugin.create_and_start_container_for_platforms'
-> 500 Server Error: Internal Server Error ("{"message":"Get
https://10.12.5.80:5000/v1/_ping: http: server gave HTTP response to HTTPS
client"}")” Is this a new Nexus docker registry that only supports http?
Lusheng
From: <[email protected]> on behalf of Gary Wu
<[email protected]>
Date: Thursday, January 11, 2018 at 11:41 AM
To: onap-discuss <[email protected]>
Subject: [onap-discuss] [dcae] DCAE failing in Amsterdam MR
Hi DCAE team,
Since last night the Amsterdam MR has been failing to spin up DCAE components.
Can you take a look?
You can use the SB-05 environment to debug the issue.
Thanks,
Gary
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
