subject:"Re\: \[onap\-discuss\] SDNC container keeps failing"

Re: [onap-discuss] SDNC container keeps failing

2017-05-24 Thread Alex Vicol (avicol)

Thanks Josef,

Indeed the /etc/resolv.conf in all the sdnc containers contains dummy values 
instead of the expected entries:


root@7d1a4e03a38d:/# cat /etc/resolv.conf

search cisco.com

nameserver 127.0.0.11

options ndots:0

The difference in my case I guess is that my sdnc VM resolv.conf looks correct. 
I checked other VMs and their containers and they are all in sync and using the 
right dns entries. Looks like it’s only the sdnc containers getting the wrong 
info. Is there a proper way to force the sdnc containers to get the right info?
I will try to change the compose file to manually change the dns config, hope 
it fixes the problem for now.

Thanks,
Alex
From: Josef Reisinger <josef.reisin...@de.ibm.com>
Date: Wednesday, May 24, 2017 at 12:53 AM
To: "Alex Vicol (avicol)" <avi...@cisco.com>
Cc: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] SDNC container keeps failing

Alex,

I can see the getaddrinfo ENOTFOUND error which hit me too as few days ago. For 
me it could be resolved with a bit weird change of the resolv.conf of the SDC 
VM. See details here: 
https://wiki.onap.org/questions/5734531/sdnc---portal-container-error-npm-err-network-getaddrinfo-enotfound<https://wiki.onap.org/questions/5734531/sdnc---portal-container-error-npm-err-network-getaddrinfo-enotfound>

Mit freundlichen Grüßen / Kind regards
Josef Reisinger
When wisdom comes to call, there's nobody listening at all - Pendragon / Man Of 
Nomadic Traits

IBM Sales & Distribution, Communications Sector
Certified IT-Architect Telecommunications
IBM Certified Telecommunications Industry ITA
Lehrbeauftragter an der Hochschule Fresenius

IBM Deutschland
Godesberger Allee 127
53175 Bonn Beuel

Phone:+49 151 1426 4559
Mobile:  +49-(0) 151 1426 4559
E-Mail:  josef.reisin...@de.ibm.com


IBM Deutschland GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Martina Koederitz (Vorsitzende), Nicole Reimer, Norbert 
Janzen, Dr. Christian Keller, Ivo Koerner, Stefan Lutz
Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart, HRB 
14562 / WEEE-Reg.-Nr. DE 99369940






From:"Alex Vicol (avicol)" <avi...@cisco.com>
To:"onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Date:24.05.2017 09:10
Subject:[onap-discuss]  SDNC container keeps failing
Sent by:onap-discuss-boun...@lists.onap.org




Hi everyone,

One of the sdnc containers (the portal_container) keeps failing in our 
Openstack deployment. Using 1.0-STAGING-latestas the docker version. Looks like 
it’s complaining about a network issue or a missing “debug” module, but not 
clear what the problem is. Overall the ONAP deployment is up and running fine: 
portal, sdc, vid, appc, … I’m able to run the demo part until the preload part. 
That’s where it’s complaining about the sdnc portal being down.

root@vm1-sdnc:/opt# docker ps
CONTAINER IDIMAGE   COMMAND 
 CREATED STATUS  PORTS NAMES
8900dc6eb41fopenecomp/dgbuilder-sdnc-image:latest   "/bin/bash -c 'cd 
..."   2 hours ago Up 2 hours  0.0.0.0:3000->3100/tcp
sdnc_dgbuilder_container
809db6dad2dcopenecomp/admportal-sdnc-image:latest   "/bin/bash -c 'cd 
..."   2 hours ago Up 4 seconds0.0.0.0:8843->8843/tcp
sdnc_portal_container
d91cf4c9470bopenecomp/sdnc-image:latest 
"/opt/openecomp/sd..."   2 hours ago Up 2 hours  
0.0.0.0:8282->8181/tcpsdnc_controller_container
d9987a61cbbemysql/mysql-server:5.6  "/entrypoint.sh 
my..."   7 days ago  Up 6 days   0.0.0.0:32768->3306/tcp   
sdnc_db_container
root@vm1-sdnc:/opt#
root@vm1-sdnc:/opt# docker logs sdnc_portal_container
npm http GET https://registry.npmjs.org/debug
npm http GET https://registry.npmjs.org/ejs
npm http GET https://registry.npmjs.org/express
npm http GET https://registry.npmjs.org/express-session
npm http GET https://registry.npmjs.org/fs.extra
npm http GET https://registry.npmjs.org/lodash
npm http GET https://registry.npmjs.org/moment
npm http GET https://registry.npmjs.org/morgan
npm http GET https://registry.npmjs.org/multer
npm http GET https://registry.npmjs.org/mysql
npm http GET https://registry.npmjs.org/node-uuid
npm http GET https://registry.npmjs.org/path
npm http GET https://registry.npmjs.org/properties-reader/0.0.9
npm http GET https://registry.npmjs.org/sax
npm http GET https://registry.npmjs.org/body-parser
npm http GET https://registry.npmjs.org/serve-favicon
npm http GET https://registry.npmjs.org/xml2js
npm http GET https://registry.npmjs.org/dns-sync
npm http GET https://registry.npmjs.org/bootstrap
npm http GET https://registry.npmjs.org/

Re: [onap-discuss] SDNC container keeps failing

2017-05-24 Thread Josef Reisinger

Alex,

I can see the getaddrinfo ENOTFOUND error which hit me too as few days 
ago. For me it could be resolved with a bit weird change of the 
resolv.conf of the SDC VM. See details here: 
https://wiki.onap.org/questions/5734531/sdnc---portal-container-error-npm-err-network-getaddrinfo-enotfound


Mit freundlichen Grüßen / Kind regards 
Josef Reisinger 
When wisdom comes to call, there's nobody listening at all - Pendragon / 
Man Of Nomadic Traits 
IBM Sales & Distribution, Communications Sector
Certified IT-Architect Telecommunications
IBM Certified Telecommunications Industry ITA
Lehrbeauftragter an der Hochschule Fresenius
IBM Deutschland 
Godesberger Allee 127 
53175 Bonn Beuel
Phone:+49 151 1426 4559 
Mobile:  +49-(0) 151 1426 4559 
E-Mail:  josef.reisin...@de.ibm.com 


IBM Deutschland GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter 
Geschäftsführung: Martina Koederitz (Vorsitzende), Nicole Reimer, Norbert 
Janzen, Dr. Christian Keller, Ivo Koerner, Stefan Lutz 
Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart, 
HRB 14562 / WEEE-Reg.-Nr. DE 99369940 




From:   "Alex Vicol (avicol)" 
To: "onap-discuss@lists.onap.org" 
Date:   24.05.2017 09:10
Subject:[onap-discuss]  SDNC container keeps failing
Sent by:onap-discuss-boun...@lists.onap.org



Hi everyone,
 
One of the sdnc containers (the portal_container) keeps failing in our 
Openstack deployment. Using 1.0-STAGING-latest as the docker version. 
Looks like it?s complaining about a network issue or a missing ?debug? 
module, but not clear what the problem is. Overall the ONAP deployment is 
up and running fine: portal, sdc, vid, appc, ? I?m able to run the demo 
part until the preload part. That?s where it?s complaining about the sdnc 
portal being down.
 
root@vm1-sdnc:/opt# docker ps
CONTAINER IDIMAGE   COMMAND   
CREATED STATUS  PORTS NAMES
8900dc6eb41fopenecomp/dgbuilder-sdnc-image:latest   "/bin/bash -c 
'cd ..."   2 hours ago Up 2 hours  0.0.0.0:3000->3100/tcp  
 sdnc_dgbuilder_container
809db6dad2dcopenecomp/admportal-sdnc-image:latest   "/bin/bash -c 
'cd ..."   2 hours ago Up 4 seconds0.0.0.0:8843->8843/tcp  
 sdnc_portal_container
d91cf4c9470bopenecomp/sdnc-image:latest "/opt/openecomp/sd..."   2 
hours ago Up 2 hours  0.0.0.0:8282->8181/tcp 
sdnc_controller_container
d9987a61cbbemysql/mysql-server:5.6 "/entrypoint.sh my..."   7 days 
ago  Up 6 days   0.0.0.0:32768->3306/tcp sdnc_db_container
root@vm1-sdnc:/opt#
root@vm1-sdnc:/opt# docker logs sdnc_portal_container
npm http GET https://registry.npmjs.org/debug
npm http GET https://registry.npmjs.org/ejs
npm http GET https://registry.npmjs.org/express
npm http GET https://registry.npmjs.org/express-session
npm http GET https://registry.npmjs.org/fs.extra
npm http GET https://registry.npmjs.org/lodash
npm http GET https://registry.npmjs.org/moment
npm http GET https://registry.npmjs.org/morgan
npm http GET https://registry.npmjs.org/multer
npm http GET https://registry.npmjs.org/mysql
npm http GET https://registry.npmjs.org/node-uuid
npm http GET https://registry.npmjs.org/path
npm http GET https://registry.npmjs.org/properties-reader/0.0.9
npm http GET https://registry.npmjs.org/sax
npm http GET https://registry.npmjs.org/body-parser
npm http GET https://registry.npmjs.org/serve-favicon
npm http GET https://registry.npmjs.org/xml2js
npm http GET https://registry.npmjs.org/dns-sync
npm http GET https://registry.npmjs.org/bootstrap
npm http GET https://registry.npmjs.org/bootstrap-table
npm http GET https://registry.npmjs.org/cookie-parser
npm http GET https://registry.npmjs.org/csv
npm http GET https://registry.npmjs.org/csvtojson
npm http GET https://registry.npmjs.org/dateformat
npm http GET https://registry.npmjs.org/bootstrap-submenu
npm http GET https://registry.npmjs.org/debug
npm http GET https://registry.npmjs.org/ejs
npm http GET https://registry.npmjs.org/express-session
npm http GET https://registry.npmjs.org/express
npm http GET https://registry.npmjs.org/fs.extra
npm http GET https://registry.npmjs.org/lodash
npm http GET https://registry.npmjs.org/moment
npm http GET https://registry.npmjs.org/morgan
npm http GET https://registry.npmjs.org/multer
npm http GET https://registry.npmjs.org/mysql
npm http GET https://registry.npmjs.org/node-uuid
npm http GET https://registry.npmjs.org/path
npm http GET https://registry.npmjs.org/properties-reader/0.0.9
npm http GET https://registry.npmjs.org/sax
npm http GET https://registry.npmjs.org/body-parser
npm http GET https://registry.npmjs.org/serve-favicon
npm http GET https://registry.npmjs.org/xml2js
npm http GET https://registry.npmjs.org/dns-sync
npm http GET https://registry.npmjs.org/bootstrap
npm http GET https://registry.npmjs.org/bootstrap-table
npm http

Re: [onap-discuss] SDNC container keeps failing

Re: [onap-discuss] SDNC container keeps failing

2 matches

Site Navigation

Mail list logo

Footer information