Ok, as long as we know what the issue was, I’ll think of a workaround. I’ll probably end up customizing the wind river heat template to exclude dcae-bootstrap VM from using the local docker cache, as you described.
Thanks for your help! -Gary From: JI, LUSHENG (LUSHENG) [mailto:[email protected]] Sent: Thursday, January 11, 2018 5:46 PM To: Gary Wu <[email protected]>; onap-discuss <[email protected]> Subject: Re: [onap-discuss] [dcae] DCAE failing in Amsterdam MR Gary, Unfortunately, that is not an easy fix. Is it possible to add https to this registry? If not, This is what I did to fix SB-05: getting into dcae-bootstrap vm and run this: sudo sed -ie 's/10.12.5.80:5000/nexus3.onap.org:10001/g' /opt/app/config/invinputs.yaml /opt/config/nexus_docker_repo.txt then rerun /opt/dcae2_vm_init.sh. Lusheng From: Gary Wu <[email protected]<mailto:[email protected]>> Date: Thursday, January 11, 2018 at 4:22 PM To: "JI, LUSHENG (LUSHENG)" <[email protected]<mailto:[email protected]>>, onap-discuss <[email protected]<mailto:[email protected]>> Subject: RE: [onap-discuss] [dcae] DCAE failing in Amsterdam MR Hi Lusheng, 10.12.5.80 is a docker cache local within the Wind River lab that allows us to dramatically speed up ONAP spin-up. Unfortunately it only supports http. The workaround for this is to configure the VM to allow insecure registries (https://docs.docker.com/registry/insecure/#deploy-a-plain-http-registry<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.docker.com_registry_insecure_-23deploy-2Da-2Dplain-2Dhttp-2Dregistry&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=qiKb3LQBLje9oy8MjG3MEx1ia4mIocif7RoUY8WQWV8&m=no6u8eU2sMS-ZZgmw72jdYWCXKu7zOb3N7jDohx57kk&s=94kty_l5rBn9juSJSTqucU3orKroBcIV_LVReU9SqyU&e=>) by adding a /etc/docker/daemon.json file with the following content: { "insecure-registries" : ["10.12.5.80:5000"] } Is this something that can be added/configured in the DCAE VMs relatively easily? For all the other VMs I was able to add such a file by modifying the heat template, but it’s not clear how we can do so for the DCAE VMs. Thanks, Gary From: JI, LUSHENG (LUSHENG) [mailto:[email protected]] Sent: Thursday, January 11, 2018 1:01 PM To: Gary Wu <[email protected]<mailto:[email protected]>>; onap-discuss <[email protected]<mailto:[email protected]>> Subject: Re: [onap-discuss] [dcae] DCAE failing in Amsterdam MR 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<https://urldefense.proofpoint.com/v2/url?u=https-3A__10.12.5.80-3A5000_v1_-5Fping&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=qiKb3LQBLje9oy8MjG3MEx1ia4mIocif7RoUY8WQWV8&m=no6u8eU2sMS-ZZgmw72jdYWCXKu7zOb3N7jDohx57kk&s=eDqWd1WmvllOioDUDAC8cQY6sfbgNfbZ6QAgFGno8qk&e=>: http: server gave HTTP response to HTTPS client"}")” Is this a new Nexus docker registry that only supports http? Lusheng From: <[email protected]<mailto:[email protected]>> on behalf of Gary Wu <[email protected]<mailto:[email protected]>> Date: Thursday, January 11, 2018 at 11:41 AM To: onap-discuss <[email protected]<mailto:[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
