Hi Marco,
In addition to below , I also noticed that there is an issue with
/opt/sdnc/installation/src/main/yaml/docker-compose.yml .
It points to openecomp/images instead of onap
sdnc:
image: openecomp/sdnc-image:latest
During the installation it seems like this code is pulled from release-1.1.0
branch :
As a result we fail :
Status: Image is up to date for
nexus3.onap.org:10001/onap/sdnc-dmaap-listener-image:1.2-STAGING-latest
Pulling sdnc (openecomp/sdnc-image:latest)...
ERROR: {"message":"repository openecomp/sdnc-image not found: does not exist or
no pull access"}
Thanks
Geora Barsky
Amdocs Technology
647-688-1039
[amdocs-a]
Follow us on Facebook<http://www.facebook.com/amdocs/>,
Twitter<http://twitter.com/amdocs>,
LinkedIn<http://www.linkedin.com/company/amdocs>,
YouTube<http://www.youtube.com/amdocsinc>,
Google+<https://plus.google.com/105657940751678445194> and the Amdocs blog
network<http://blogs.amdocs.com/>.
From: [email protected]
[mailto:[email protected]] On Behalf Of PLATANIA, MARCO
(MARCO)
Sent: Wednesday, November 15, 2017 1:27 PM
To: Arun Arora <[email protected]>; [email protected];
[email protected]; Michael O'Brien <[email protected]>
Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails
Arun, Sylvain, Michael,
I ran docker pull for SDNC WindRiver and it worked. I noticed the same issue
with MSB though, because the docker version in Heat is wrong. It is v1.0.0,
while it should be 1.0.0 (without v). I’m going to submit a change soon, please
update your local Heat env.
Arun,
If you are using an old heat template, please switch to the latest one:
https://gerrit.onap.org/r/gitweb?p=demo.git;a=tree;f=heat/ONAP;h=f948399f5fcbe2300f0d7b8417792aea4682425d;hb=refs/heads/master
/opt/config/nexus_docker_repo.txt in the SDNC VM is used by the vm_init script
to point to the Nexus repository. Make sure you have port 10001 instead of
10003 in that file.
Marco
From:
<[email protected]<mailto:[email protected]>>
on behalf of Arun Arora <[email protected]<mailto:[email protected]>>
Date: Wednesday, November 15, 2017 at 12:23 PM
To: "[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>
Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails
Following JIRA Ticket:
https://jira.onap.org/browse/SDNC-102<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_SDNC-2D102&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=jJs8089honCN-dSntDLJkfuXkr4ZTgk-PpoTTqBomVc&s=asydkDlpEShSZQIMXuHNQ7zrJgNmbroB84JkI_eCamY&e=>
was created for this issue and marked as Resolved and Closed. However, the
issue still seems to be present.
In comments it was mentioned to change the port from 10003 to 10001 in
docker-compose.yml.
But I didn't find any such port in
/opt/sdnc/installation/src/main/yaml/docker-compose.yml.
Can someone provide me a working hack..
Thanks,
Arun Arora
[SDNC-102] SDNC Failed Robot Health Check -
ONAP<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_SDNC-2D102&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=jJs8089honCN-dSntDLJkfuXkr4ZTgk-PpoTTqBomVc&s=asydkDlpEShSZQIMXuHNQ7zrJgNmbroB84JkI_eCamY&e=>
jira.onap.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__jira.onap.org&d=DwQFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=jJs8089honCN-dSntDLJkfuXkr4ZTgk-PpoTTqBomVc&s=ZcMPuZKSmxB27OcQnSd9LjOVMVY_LGpM_PDUduDlfFc&e=>
No reviews matched the request. Check your Options in the drop-down menu of
this sections header.
________________________________
From:
[email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>>
on behalf of Arun Arora <[email protected]<mailto:[email protected]>>
Sent: Wednesday, November 15, 2017 10:37:33 PM
To: [email protected]<mailto:[email protected]>
Subject: [onap-discuss] [SDNC] sdnc_vm_init.sh fails
ERROR: {"message":"repository onap/sdnc-image not found: does not exist or no
pull access"}
Hi All,
I am seeing this error since yesterday. I tried to re-pull SDNC dockers afresh.
For that I deleted all dockers along with all the files/ directories downloaded
in /opt when sdnc_install.sh runs.
I tried this many times but the I receive the same error above in each trial.
What may be the reason of this error? I doubt it is some local setup issue as I
re-pulled other VMs as well along with SDNC but didn't see any such error.
Is this seen by someone else? Any possible solutions?
Thanks,
Arun Arora
This message and the information contained herein is proprietary and
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
<https://www.amdocs.com/about/email-disclaimer>
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
