The SDC disk partitioning process has been revisited when we built the template for Vanilla OpenStack. Rackspace uses xdvb while other platforms use vdb. I checked ONAP installations in my lab, and they all seem to work fine, please see below.
Vikram, Did you change some configuration by any chance? Or is it related to the Ubuntu image you are using? Thanks, Marco ubuntu at vm1-sdc:~$ sudo fdisk -l Disk /dev/vda: 160 GiB, 171798691840 bytes, 335544320 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x83cfa932 Device Boot Start End Sectors Size Id Type /dev/vda1 * 2048 335544286 335542239 160G 83 Linux Disk /dev/vdb: 100 GiB, 107374182400 bytes, 209715200 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xd35c67e0 Device Boot Start End Sectors Size Id Type /dev/vdb1 2048 209715199 209713152 100G 83 Linux ubuntu at vm1-sdc:~$ sudo df -h Filesystem Size Used Avail Use% Mounted on udev 7.9G 0 7.9G 0% /dev tmpfs 1.6G 12M 1.6G 1% /run /dev/vda1 156G 6.0G 150G 4% / tmpfs 7.9G 2.2M 7.9G 1% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup /dev/vdb1 99G 1.2G 93G 2% /data none 156G 6.0G 150G 4% /var/lib/docker/aufs/mnt/8e983cdd8954a698416949c4f9360b2e03481fa4f4b039fdb78094c97a03ae7a shm 64M 0 64M 0% /var/lib/docker/containers/3dc371d3b6ef6d4fcd2192a43cbae86dc5b7e89b8300f63637029541514dc103/shm none 156G 6.0G 150G 4% /var/lib/docker/aufs/mnt/214bcfd365fec8b2ad0742046de6a455bde5b9219abe91a81ebcf473c429e34e shm 64M 0 64M 0% /var/lib/docker/containers/58e8e1160ef3b42672a0b9644c54e55c21c894c822a9f6203436c3fe1a6f727b/shm none 156G 6.0G 150G 4% /var/lib/docker/aufs/mnt/2555568bfc1e11dbfb3633b79742192fa3a525932fefc11afb09f03f2644cb70 shm 64M 0 64M 0% /var/lib/docker/containers/be9d5862028e0e5d3cdf9d6d4f84763e521065923cb93f7a0e1575c4435b531c/shm none 156G 6.0G 150G 4% /var/lib/docker/aufs/mnt/342d57c225dee7739aef8bd2c627a63f5fcecc98218f0b9b2f174d79f3281083 shm 64M 0 64M 0% /var/lib/docker/containers/85310c18c9addc1849017de132df72444f329a2a6c3fa60f6ee8c8b3c2ecae77/shm none 156G 6.0G 150G 4% /var/lib/docker/aufs/mnt/cdb5c0081921e87f4d635d62fac92773a5d77f8c4a29ee5175d0315e0374718e shm 64M 0 64M 0% /var/lib/docker/containers/3ada50f66cb39e4c2b23cc62fdfc173948f4ebabb40ecb49959d5b174fd21811/shm tmpfs 1.6G 0 1.6G 0% /run/user/1000 From: "FREEMAN, BRIAN D" <[email protected]> Date: Thursday, April 20, 2017 at 8:46 AM To: Vikram Mukundamgari <vikram.mukundamgari at nexius.com>, Chris Reece <creece at awardsolutions.com>, "PLATANIA, MARCO (MARCO)" <platania at research.att.com>, "Ahmad, Munir" <Munir.Ahmad at bell.ca> Subject: RE: [onap-discuss] Unable to login as designer role Marco would know better but I think this is one of those Rackspace vs Vanilla openstack issue (but I have been wrong before) Brian From: Vikram Mukundamgari [mailto:[email protected]] Sent: Wednesday, April 19, 2017 7:03 PM To: FREEMAN, BRIAN D <bf1936 at att.com>; Chris Reece <creece at awardsolutions.com>; PLATANIA, MARCO <platania at research.att.com>; Ahmad, Munir <Munir.Ahmad at bell.ca> Subject: Re: [onap-discuss] Unable to login as designer role Thanks Brian, Seems like the volume is attached to /dev/vdc instead of vdb and data directory ran out of disk space root at vm1-sdc:~# fdisk -l Disk /dev/vda: 160 GiB, 171798691840 bytes, 335544320 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xa6a12a80 Device Boot Start End Sectors Size Id Type /dev/vda1 * 2048 335544286 335542239 160G 83 Linux Disk /dev/vdb: 64 MiB, 67108864 bytes, 131072 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x2913f3b0 Device Boot Start End Sectors Size Id Type /dev/vdb1 2048 131071 129024 63M 83 Linux Disk /dev/vdc: 100 GiB, 107374182400 bytes, 209715200 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes root at vm1-sdc:~# df -h Filesystem Size Used Avail Use% Mounted on udev 7.9G 0 7.9G 0% /dev tmpfs 1.6G 13M 1.6G 1% /run /dev/vda1 156G 5.5G 150G 4% / tmpfs 7.9G 1.2M 7.9G 1% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup /dev/vdb1 58M 53M 0 100% /data none 156G 5.5G 150G 4% /var/lib/docker/aufs/mnt/ecf711bb91008c0e536f5bd9afd3f23a2b233c6d001438a7da6a8828f23d086c shm 64M 0 64M 0% /var/lib/docker/containers/0cc4f8e23249d15e7fdb79450645285d7cb84c1a57da7e375a6bd4d4b2568a24/shm none 156G 5.5G 150G 4% /var/lib/docker/aufs/mnt/fffe5e6fe80eee74ec1da357268ea1ff604b0d0be7f5b7e8536dbbfd08ea4fb6 shm 64M 0 64M 0% /var/lib/docker/containers/dc6fbe5317637475775cba5aa697af087d8cc7a78fd12a2b6d42fb4ae5f89920/shm tmpfs 1.6G 0 1.6G 0% /run/user/1000 none 156G 5.5G 150G 4% /var/lib/docker/aufs/mnt/bab1f9622e9c2b0631d0baaa728cc3f2b2504837d1813714a1cf1f0ee61b6df6 shm 64M 0 64M 0% /var/lib/docker/containers/4457fc12aad643118f2a1458ae18bb0d54352c8bef48c02a0252058f96d9bc1d/shm none 156G 5.5G 150G 4% /var/lib/docker/aufs/mnt/febd927cd0e39f4f08a9ea59ccd55a37da76d396adee237e2c3c65018678deb3 shm 64M 0 64M 0% /var/lib/docker/containers/9f038ebc1b7a80347423c1921c7c844da57ff4e797ab3937f896e012f5dd3c2e/shm none 156G 5.5G 150G 4% /var/lib/docker/aufs/mnt/b69b86a9bda57b7a8652c6905e1e6bbe379d48f7c33fca8e08d83249551998c7 shm 64M 0 64M 0% /var/lib/docker/containers/bf63edd246429d29779b30d88a5aba5de760fbbbef494a31073b288c5b96c60d/shm From: "FREEMAN, BRIAN D" <bf1936 at att.com<mailto:[email protected]>> Date: Wednesday, April 19, 2017 at 2:40 PM To: Chris Reece <creece at awardsolutions.com<mailto:creece at awardsolutions.com>>, "PLATANIA, MARCO" <platania at research.att.com<mailto:platania at research.att.com>>, "Ahmad, Munir" <Munir.Ahmad at bell.ca<mailto:Munir.Ahmad at bell.ca>>, Vikram Mukundamgari <vikram.mukundamgari at nexius.com<mailto:vikram.mukundamgari at nexius.com>> Subject: RE: [onap-discuss] Unable to login as designer role Dropping the discuss-list Is this a disk space / access to the cinder volume issue ? Suppressed: java.io.IOException: No space left on device Brian From: onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at lists.onap.org> [mailto:[email protected]] On Behalf Of Chris Reece Sent: Wednesday, April 19, 2017 5:32 PM To: PLATANIA, MARCO <platania at research.att.com<mailto:platania at research.att.com>>; Ahmad, Munir <Munir.Ahmad at bell.ca<mailto:Munir.Ahmad at bell.ca>>; Vikram Mukundamgari <vikram.mukundamgari at nexius.com<mailto:vikram.mukundamgari at nexius.com>>; onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> Subject: Re: [onap-discuss] Unable to login as designer role Hello Marco, Yes, this is one of the issues. The other is that after about an hour Titan graph fails. I?m using a Mitaka lab (specifically OPNFV Colorado). Do you want me to open a Jira ticket? Thanks, Chris [cid:image001.png at 01D2B9B4.DFA21940] Chris Reece Technologist www.AwardSolutions.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.awardsolutions.com_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=YHquXsp8I67EodhgLH7mFTwUANtyASkijDu3kyjb06A&s=DiOmp_fGazR76JECqq3wIvCw5Gwv4Vq1b2SYLzqrtkE&e=> (W) 972-664-0727 x242 [cid:image002.png at 01D2B9B4.DFA21940]<https://urldefense.proofpoint.com/v2/url?u=https-3A__devops2.awardsolutions.com_portal_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=YHquXsp8I67EodhgLH7mFTwUANtyASkijDu3kyjb06A&s=zoKg4jaeyMRJwrRgGq_DCkQW8jP1SUlG_RSk5dwAqjo&e=>[cid:image003.png at 01D2B9B4.DFA21940]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_company_award-2Dsolutions&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=YHquXsp8I67EodhgLH7mFTwUANtyASkijDu3kyjb06A&s=a4QG_cQBT7z5n-4gVXCyP1Dx4ueBxveRDXXLZfnKugc&e=>[cid:image004.png at 01D2B9B4.DFA21940]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_awardsolutions&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=YHquXsp8I67EodhgLH7mFTwUANtyASkijDu3kyjb06A&s=RJibggO5UsZYZdYmGNBkcbhp5fjswOuy_-MKe25uNdA&e=> 2100 Lakeside Blvd, Suite 300 Richardson, TX 75082 USA Recognized 9x in Best Companies to Work for in Texas Technology Training Partner of Mobile World Congress 2017 | More<https://urldefense.proofpoint.com/v2/url?u=http-3A__go.awardsolutions.com_l_147601_2017-2D02-2D07_21z4hn&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=YHquXsp8I67EodhgLH7mFTwUANtyASkijDu3kyjb06A&s=NirZjl36RtXk51VvRzvX1wiWIiLBS_Y_qbGwno8mk-Q&e=> From: PLATANIA, MARCO (MARCO) [mailto:[email protected]] Sent: Wednesday, April 19, 2017 4:18 PM To: Chris Reece <creece at awardsolutions.com<mailto:creece at awardsolutions.com>>; Ahmad, Munir <Munir.Ahmad at bell.ca<mailto:Munir.Ahmad at bell.ca>>; Vikram Mukundamgari <vikram.mukundamgari at nexius.com<mailto:vikram.mukundamgari at nexius.com>>; onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> Subject: Re: [onap-discuss] Unable to login as designer role Hello Chris, Thanks for the feedback. I can?t reproduce this issue in my lab, so we need SDC people investigate the problem. Is the problem described in this Jira ticket? https://jira.onap.org/browse/SDC-12?jql=project%20%3D%20SDC<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_SDC-2D12-3Fjql-3Dproject-2520-253D-2520SDC&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=YHquXsp8I67EodhgLH7mFTwUANtyASkijDu3kyjb06A&s=YBhSZE5hEngC-gGg62CmpQ-v7bBf77Sf1B0Tcy5GdvU&e=> If not, we?ll need to open a new one. Could you please describe your operational environment (Rackspace vs OpenStack, which OpenStack version, ?)? Thanks, Marco From: Chris Reece <creece at awardsolutions.com<mailto:[email protected]>> Date: Wednesday, April 19, 2017 at 4:11 PM To: "PLATANIA, MARCO (MARCO)" <platania at research.att.com<mailto:platania at research.att.com>>, "Ahmad, Munir" <Munir.Ahmad at bell.ca<mailto:Munir.Ahmad at bell.ca>>, Vikram Mukundamgari <vikram.mukundamgari at nexius.com<mailto:vikram.mukundamgari at nexius.com>>, "onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>" <onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>> Subject: RE: [onap-discuss] Unable to login as designer role Hello Marco, I?ve reinstalled ONAP using the parameters you mentioned below. About an hour after it launched the Titan Graph failed and I started to get a [cid:image005.png at 01D2B9B4.DFA21940] I following your advice and restarted the vm. The containers have been running for about 20 min: ubuntu at vm1-sdc:/data/scripts$ sudo docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 1f19f361ec8f nexus3.onap.org:10001/openecomp/sdc-frontend:1.0-STAGING-latest "/root/startup.sh" 20 minutes ago Up 20 minutes 0.0.0.0:8181->8181/tcp, 8080/tcp, 0.0.0.0:9443->9443/tcp sdc-FE a26bc73a5ec8 nexus3.onap.org:10001/openecomp/sdc-backend:1.0-STAGING-latest "/root/startup.sh" 21 minutes ago Up 21 minutes 0.0.0.0:8080->8080/tcp, 0.0.0.0:8443->8443/tcp sdc-BE bfa742159b81 nexus3.onap.org:10001/openecomp/sdc-kibana:1.0-STAGING-latest "/root/startup.sh" 21 minutes ago Up 21 minutes 0.0.0.0:5601->5601/tcp sdc-kbn 57d3dedaa0a0 nexus3.onap.org:10001/openecomp/sdc-cassandra:1.0-STAGING-latest "/root/startup.sh" 21 minutes ago Up 21 minutes 7000-7001/tcp, 0.0.0.0:9042->9042/tcp, 7199/tcp, 0.0.0.0:9160->9160/tcp sdc-cs 394cff54e8ea nexus3.onap.org:10001/openecomp/sdc-elasticsearch:1.0-STAGING-latest "/root/startup.sh" 21 minutes ago Up 21 minutes 0.0.0.0:9200->9200/tcp, 0.0.0.0:9300->9300/tcp sdc-es I?m still getting the same error. I?ve logged out of ONAP and logged back in with various users and same result when I click on the SDC icon. Below is a number of log files and the results of the health check. Any thoughts on what I should do? Any idea where I can look a log file to see why titan is crashing? Thanks ? Chris Here is the health check: ubuntu at vm1-sdc:/data/scripts$ ./docker_health.sh { "cluster_name" : "SDC-ES-AUTO", "status" : "red", "timed_out" : false, "number_of_nodes" : 1, "number_of_data_nodes" : 1, "active_primary_shards" : 0, "active_shards" : 0, "relocating_shards" : 0, "initializing_shards" : 1, "unassigned_shards" : 1, "delayed_unassigned_shards" : 0, "number_of_pending_tasks" : 2, "number_of_in_flight_fetch" : 0, "task_max_waiting_in_queue_millis" : 2, "active_shards_percent_as_number" : 0.0 } BE health-Check: <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/> <title>Error 503 </title> </head> <body> <h2>HTTP ERROR: 503</h2> <p>Problem accessing /sdc2/rest/healthCheck. Reason: <pre> Service Unavailable</pre></p> <hr /><a href="http://eclipse.org/jetty<https://urldefense.proofpoint.com/v2/url?u=http-3A__eclipse.org_jetty&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=YHquXsp8I67EodhgLH7mFTwUANtyASkijDu3kyjb06A&s=XcsWucuWSDXTf-rKHPIFLkDqDhr36ofX1ZL53r4a3s4&e=>">Powered by Jetty:// 9.3.15.v20161220</a><hr/> </body> </html> FE health-Check: { "sdcVersion": "UNKNOWN", "siteMode": "UNKNOWN", "componentsInfo": [ { "healthCheckComponent": "FE", "healthCheckStatus": "UP", "version": "1.0.0", "description": "OK" }, { "healthCheckComponent": "BE", "healthCheckStatus": "DOWN" }, { "healthCheckComponent": "ES", "healthCheckStatus": "UNKNOWN" }, { "healthCheckComponent": "TITAN", "healthCheckStatus": "UNKNOWN" }, { "healthCheckComponent": "DE", "healthCheckStatus": "UNKNOWN" } ] } Error [12] while user existance check Here is the sdc-cs log: [2017-04-19T19:38:20+00:00] INFO: Report handlers complete Wed Apr 19 19:38:21 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:38:27 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:38:32 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:38:38 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:38:43 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:38:49 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:38:55 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:39:00 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:39:06 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:39:11 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:39:17 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:39:22 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:39:28 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:39:34 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:39:39 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:39:45 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:39:51 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:39:56 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:40:02 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:40:07 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:40:13 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:40:18 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:40:24 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:40:29 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:40:35 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:40:40 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:40:46 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:40:51 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:40:57 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:41:02 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:41:08 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:41:13 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:41:19 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:41:25 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:41:30 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:41:36 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:41:41 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:41:47 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:41:52 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:41:58 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:42:03 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:42:09 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:42:14 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:42:20 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:42:25 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:42:31 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:42:36 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:42:42 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:42:48 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:42:53 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:42:58 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:43:04 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:43:09 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:43:15 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:43:20 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:43:26 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:43:32 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:43:37 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:43:43 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:43:48 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:43:54 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:43:59 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:44:05 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:44:10 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:44:16 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:44:22 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:44:27 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:44:33 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:44:38 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:44:44 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:44:49 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:44:55 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:45:01 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:45:06 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:45:12 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:45:17 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:45:23 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:45:28 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:45:34 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:45:39 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:45:45 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:45:50 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:45:56 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:46:01 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:46:07 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:46:12 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:46:18 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:46:24 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:46:29 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:46:35 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:46:40 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:46:46 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:46:51 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:46:57 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:47:02 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:47:08 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:47:13 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:47:19 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:47:24 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 Wed Apr 19 19:47:30 UTC 2017 --- cqlsh is NOT enabled to connect yet. sleep 5 pass_changed=[99] pass_changed doen't have value keyspace is empty, probably connection error. Exit... java -Dlogback.configurationFile=/tmp/./sdctool/scripts/../config/logback.xml -cp ::/tmp/./sdctool/scripts/../sdctool-1.0.0-jar-with-dependencies.jar: org.openecomp.sdc.asdctool.main.DataSchemaMenu create-cassandra-structures /tmp/sdctool/config *********************************** ***** 2 ********************* The log for sdc-es just repeats the following: [2017-04-19 20:03:13,195][WARN ][gateway ] [394cff54e8ea] [.kibana]: failed to write index state java.io.IOException: No space left on device at sun.nio.ch.FileDispatcherImpl.write0(Native Method) at sun.nio.ch.FileDispatcherImpl.write(FileDispatcherImpl.java:60) at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93) at sun.nio.ch.IOUtil.write(IOUtil.java:65) at sun.nio.ch.FileChannelImpl.write(FileChannelImpl.java:211) at java.nio.channels.Channels.writeFullyImpl(Channels.java:78) at java.nio.channels.Channels.writeFully(Channels.java:101) at java.nio.channels.Channels.access$000(Channels.java:61) at java.nio.channels.Channels$1.write(Channels.java:174) at java.util.zip.CheckedOutputStream.write(CheckedOutputStream.java:73) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140) at org.apache.lucene.store.OutputStreamIndexOutput.getChecksum(OutputStreamIndexOutput.java:80) at org.apache.lucene.codecs.CodecUtil.writeCRC(CodecUtil.java:471) at org.apache.lucene.codecs.CodecUtil.writeFooter(CodecUtil.java:310) at org.elasticsearch.gateway.MetaDataStateFormat.write(MetaDataStateFormat.java:129) at org.elasticsearch.gateway.MetaStateService.writeIndex(MetaStateService.java:135) at org.elasticsearch.gateway.GatewayMetaState.clusterChanged(GatewayMetaState.java:160) at org.elasticsearch.gateway.Gateway.clusterChanged(Gateway.java:185) at org.elasticsearch.cluster.service.InternalClusterService$UpdateTask.run(InternalClusterService.java:494) at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:231) at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:194) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Suppressed: java.io.IOException: No space left on device at sun.nio.ch.FileDispatcherImpl.write0(Native Method) at sun.nio.ch.FileDispatcherImpl.write(FileDispatcherImpl.java:60) at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93) at sun.nio.ch.IOUtil.write(IOUtil.java:65) at sun.nio.ch.FileChannelImpl.write(FileChannelImpl.java:211) at java.nio.channels.Channels.writeFullyImpl(Channels.java:78) at java.nio.channels.Channels.writeFully(Channels.java:101) at java.nio.channels.Channels.access$000(Channels.java:61) at java.nio.channels.Channels$1.write(Channels.java:174) at java.util.zip.CheckedOutputStream.write(CheckedOutputStream.java:73) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140) at org.apache.lucene.store.OutputStreamIndexOutput.close(OutputStreamIndexOutput.java:68) at org.elasticsearch.gateway.MetaDataStateFormat.write(MetaDataStateFormat.java:130) ... 9 more Suppressed: java.io.IOException: No space left on device at sun.nio.ch.FileDispatcherImpl.write0(Native Method) at sun.nio.ch.FileDispatcherImpl.write(FileDispatcherImpl.java:60) at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93) at sun.nio.ch.IOUtil.write(IOUtil.java:65) at sun.nio.ch.FileChannelImpl.write(FileChannelImpl.java:211) at java.nio.channels.Channels.writeFullyImpl(Channels.java:78) at java.nio.channels.Channels.writeFully(Channels.java:101) at java.nio.channels.Channels.access$000(Channels.java:61) at java.nio.channels.Channels$1.write(Channels.java:174) at java.util.zip.CheckedOutputStream.write(CheckedOutputStream.java:73) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140) at java.io.FilterOutputStream.close(FilterOutputStream.java:158) at org.apache.lucene.store.OutputStreamIndexOutput.close(OutputStreamIndexOutput.java:70) ... 10 more sdc-be seems to fail: [2017-04-19T19:40:59+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1) sdc-kbn has the following failure: [WARN tini (235)] Tini is not running as PID 1 and isn't registered as a child subreaper. Zombie processes will not be re-parented to Tini, so zombie reaping won't work. To fix the problem, use -s or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1. {"type":"log","@timestamp":"2017-04-19T19:38:45+00:00","tags":["info","optimize"],"pid":241,"message":"Optimizing and caching bundles for kibana and statusPage. This may take a few minutes"} {"type":"log","@timestamp":"2017-04-19T19:39:35+00:00","tags":["info","optimize"],"pid":241,"message":"Optimization of bundles for kibana and statusPage complete in 50.63 seconds"} {"type":"log","@timestamp":"2017-04-19T19:39:35+00:00","tags":["status","plugin:kibana","info"],"pid":241,"name":"plugin:kibana","state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-04-19T19:39:35+00:00","tags":["status","plugin:elasticsearch","info"],"pid":241,"name":"plugin:elasticsearch","state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-04-19T19:39:35+00:00","tags":["status","plugin:kbn_vislib_vis_types","info"],"pid":241,"name":"plugin:kbn_vislib_vis_types","state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-04-19T19:39:35+00:00","tags":["status","plugin:elasticsearch","error"],"pid":241,"name":"plugin:elasticsearch","state":"red","message":"Status changed from yellow to red - Service Unavailable","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2017-04-19T19:39:35+00:00","tags":["status","plugin:markdown_vis","info"],"pid":241,"name":"plugin:markdown_vis","state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-04-19T19:39:35+00:00","tags":["status","plugin:metric_vis","info"],"pid":241,"name":"plugin:metric_vis","state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-04-19T19:39:35+00:00","tags":["status","plugin:spyModes","info"],"pid":241,"name":"plugin:spyModes","state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-04-19T19:39:35+00:00","tags":["status","plugin:statusPage","info"],"pid":241,"name":"plugin:statusPage","state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-04-19T19:39:35+00:00","tags":["status","plugin:table_vis","info"],"pid":241,"name":"plugin:table_vis","state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-04-19T19:39:35+00:00","tags":["listening","info"],"pid":241,"message":"Server running at http://0.0.0.0:5601<https://urldefense.proofpoint.com/v2/url?u=http-3A__0.0.0.0-3A5601&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=YHquXsp8I67EodhgLH7mFTwUANtyASkijDu3kyjb06A&s=D9gGq_c3iqJ8SQB9YEvoyp2xzCnea7A-YnlTRzFCots&e=>"} [cid:image006.png at 01D2B9B4.DFA21940] Chris Reece Technologist www.AwardSolutions.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.awardsolutions.com_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=XmuFtknQBvEcy1HXtAp30UIR4eB3z9nN_NtfZDE9O_A&s=rtYSWO4vFBGqX644CRh-mnMdMCpIf3kd1kA8W7PXziw&e=> (W) 972-664-0727 x242 [cid:image007.png at 01D2B9B4.DFA21940]<https://urldefense.proofpoint.com/v2/url?u=https-3A__devops2.awardsolutions.com_portal_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=XmuFtknQBvEcy1HXtAp30UIR4eB3z9nN_NtfZDE9O_A&s=eOUNevepzPwxtOdQOIQAOSxvk4jECKSdAXZU77iPgz8&e=>[cid:image008.png at 01D2B9B4.DFA21940]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_company_award-2Dsolutions&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=XmuFtknQBvEcy1HXtAp30UIR4eB3z9nN_NtfZDE9O_A&s=JxGPnwj2ePrZiuenvgq6filNKV7PxBsLIgxm511TbUI&e=>[cid:image009.png at 01D2B9B4.DFA21940]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_awardsolutions&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=XmuFtknQBvEcy1HXtAp30UIR4eB3z9nN_NtfZDE9O_A&s=FPS2ciHKW4NPJ0NAjR6l5310JbmTvFxH3YcQ8Bd1jek&e=> 2100 Lakeside Blvd, Suite 300 Richardson, TX 75082 USA Recognized 9x in Best Companies to Work for in Texas Technology Training Partner of Mobile World Congress 2017 | More<https://urldefense.proofpoint.com/v2/url?u=http-3A__go.awardsolutions.com_l_147601_2017-2D02-2D07_21z4hn&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=XmuFtknQBvEcy1HXtAp30UIR4eB3z9nN_NtfZDE9O_A&s=v8RQGfz5GVXXeOL4txkRl-ZifI35riXnKlSEHxyBmqE&e=> From: PLATANIA, MARCO (MARCO) [mailto:[email protected]] Sent: Wednesday, April 19, 2017 1:15 PM To: Chris Reece <creece at awardsolutions.com<mailto:creece at awardsolutions.com>>; Ahmad, Munir <Munir.Ahmad at bell.ca<mailto:Munir.Ahmad at bell.ca>>; Vikram Mukundamgari <vikram.mukundamgari at nexius.com<mailto:vikram.mukundamgari at nexius.com>>; onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> Subject: Re: [onap-discuss] Unable to login as designer role Hello Chris, Thanks for the feedback. The parameters in the environment file should be * artifacts_version: 1.0.0 * docker_version: 1.0-STAGING-latest This is the scenario we have been testing for long time and seems pretty stable. Those parameters are valid even if you are downloading the heat template in 1.1.0. I suggest you to use that setup. Thanks, Marco From: Chris Reece <creece at awardsolutions.com<mailto:[email protected]>> Date: Wednesday, April 19, 2017 at 2:03 PM To: "PLATANIA, MARCO (MARCO)" <platania at research.att.com<mailto:platania at research.att.com>>, "Ahmad, Munir" <Munir.Ahmad at bell.ca<mailto:Munir.Ahmad at bell.ca>>, Vikram Mukundamgari <vikram.mukundamgari at nexius.com<mailto:vikram.mukundamgari at nexius.com>>, "onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>" <onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>> Subject: RE: [onap-discuss] Unable to login as designer role Hello Marco, My experience has been once the system gets into this state where the titan graph fails, no matter what I do the services remain unreachable. I?ve tried rebooting, restarting the containers, and stopping all the containers then restarting them. In every attempt to restart I end up with the FE active, BE down, and the others unknown from a health status perspective. Just to verify, in the environment file I changed the following parameters: - artifacts_version: from 1.0.0 to 1.1.0-SNAPSHOT - docker_version: from 1.0-STAGING-latest to latest Is this correct? Thanks, Chris [cid:image010.png at 01D2B9B4.DFA21940] Chris Reece Technologist www.AwardSolutions.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.awardsolutions.com_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=Q8gftAHfnn9y-OAIW2oh1IvZkZPU9Lnfkvfw9KBDDXM&s=bhoLLfHGLNy2P4vUqerYRKefd0K7n8-cc4XNSNyJyfw&e=> (W) 972-664-0727 x242 [cid:image011.png at 01D2B9B4.DFA21940]<https://urldefense.proofpoint.com/v2/url?u=https-3A__devops2.awardsolutions.com_portal_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=Q8gftAHfnn9y-OAIW2oh1IvZkZPU9Lnfkvfw9KBDDXM&s=DUViLoUWbk1OGaF8QAzPZWAg7SWveNg4EkAiPtkRPdY&e=>[cid:image012.png at 01D2B9B4.DFA21940]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_company_award-2Dsolutions&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=Q8gftAHfnn9y-OAIW2oh1IvZkZPU9Lnfkvfw9KBDDXM&s=aJeXnGvwY0Cv_RmZSbiJ-BybsoOG8rvc7fRJ6bSg1_8&e=>[cid:image013.png at 01D2B9B4.DFA21940]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_awardsolutions&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=Q8gftAHfnn9y-OAIW2oh1IvZkZPU9Lnfkvfw9KBDDXM&s=lHF2c5l4mzAa7D9WCoxX0cQsyP_rIXDxA5jiytmvUNo&e=> 2100 Lakeside Blvd, Suite 300 Richardson, TX 75082 USA Recognized 9x in Best Companies to Work for in Texas Technology Training Partner of Mobile World Congress 2017 | More<https://urldefense.proofpoint.com/v2/url?u=http-3A__go.awardsolutions.com_l_147601_2017-2D02-2D07_21z4hn&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=Q8gftAHfnn9y-OAIW2oh1IvZkZPU9Lnfkvfw9KBDDXM&s=jyH-gBipPR-M0358jLpg16tBPMOo67qXdLuPJ5n0EnI&e=> From: PLATANIA, MARCO (MARCO) [mailto:[email protected]] Sent: Wednesday, April 19, 2017 12:55 PM To: Ahmad, Munir <Munir.Ahmad at bell.ca<mailto:Munir.Ahmad at bell.ca>>; Chris Reece <creece at awardsolutions.com<mailto:creece at awardsolutions.com>>; Vikram Mukundamgari <vikram.mukundamgari at nexius.com<mailto:vikram.mukundamgari at nexius.com>>; onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> Subject: Re: [onap-discuss] Unable to login as designer role Chris, All, As a rule of thumb, you can simply reboot the VM to restart the containers from a fresh environment or pick up the latest changes to docker images. This logic is included in the asdc_vm_init.sh script (for the SDC VM) that runs at any (re)boot of the VM. You don?t need to reinstall the entire ONAP platform. Thanks, Marco From: "Ahmad, Munir" <Munir.Ahmad at bell.ca<mailto:[email protected]>> Date: Wednesday, April 19, 2017 at 12:34 PM To: Chris Reece <creece at awardsolutions.com<mailto:creece at awardsolutions.com>>, Vikram Mukundamgari <vikram.mukundamgari at nexius.com<mailto:vikram.mukundamgari at nexius.com>>, "PLATANIA, MARCO (MARCO)" <platania at research.att.com<mailto:platania at research.att.com>>, "onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>" <onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>> Subject: Re: [onap-discuss] Unable to login as designer role Hi Chris, Try restarting just sdc-cs (highlighted) and if it doesn?t work then you need to restart the containers in the following order checking docker logs after each restart to ensure it has fully come up before going to the next one: docker restart sdc-es docker restart sdc-cs docker restart sdc-kbn docker restart sdc-BE docker restart sdc-FE docker logs sdc-cs will give you docker logs for Cassandra container. Thanks Munir From: Chris Reece <creece at awardsolutions.com<mailto:[email protected]>> Date: Wednesday, April 19, 2017 at 12:27 PM To: "Ahmad, Munir" <Munir.Ahmad at bell.ca<mailto:Munir.Ahmad at bell.ca>>, Vikram Mukundamgari <vikram.mukundamgari at nexius.com<mailto:vikram.mukundamgari at nexius.com>>, "PLATANIA, MARCO (MARCO)" <platania at research.att.com<mailto:platania at research.att.com>>, "onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>" <onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>> Subject: RE: [onap-discuss] Unable to login as designer role Hello Munir, I reinstalled ONAP today and SDC was working for about an hour before the Titan Graph went down. At that point I was only getting service unavailable errors. Titan Graph failed while going through an onboarding process. I looked at the logs for the Cassandra container (which is where I am assuming Titan is running since it?s associated with Cassandra) and I saw the following error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGBUS (0x7) at pc=0x00007f16f8c3d0f2, pid=224, tid=0x00007f16e5428700 # # JRE version: OpenJDK Runtime Environment (8.0_121-b13) (build 1.8.0_121-8u121-b13-1~bpo8+1-b13) # Java VM: OpenJDK 64-Bit Server VM (25.121-b13 mixed mode linux-amd64 compressed oops) # Problematic frame: # v ~StubRoutines::jbyte_disjoint_arraycopy # # Core dump written. Default location: /root/chef-solo/core or core.224 # # An error report file with more information is saved as: # /tmp/hs_err_pid224.log I tried to look in these directories for the log, but I couldn?t find them. Any thoughts? Is there a way to restart Titan or the Cassandra container without having to go through a rebuild of ONAP (losing all of the onboarded VNFs in the process). Thanks, Chris [cid:image014.png at 01D2B9B4.DFA21940] Chris Reece Technologist www.AwardSolutions.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.awardsolutions.com_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=bs4SWoTyj76sfLy5RIs71-4bw3SXARLFfB8r2JwrOo4&e=> (W) 972-664-0727 x242 [cid:image015.png at 01D2B9B4.DFA21940]<https://urldefense.proofpoint.com/v2/url?u=https-3A__devops2.awardsolutions.com_portal_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=HQ2r3XRpsYTt_tAlvzUSh4QA-c4L5ZrD0gLO2toR0HI&e=>[cid:image016.png at 01D2B9B4.DFA21940]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_company_award-2Dsolutions&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=FMvGOflg1evat6O-PD1lQHXeYK2q6okI0Q0kuS65Q0M&e=>[cid:image017.png at 01D2B9B4.DFA21940]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_awardsolutions&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=F0HrEfG5C2It8RoC07_2VITEt8m2HXC2leQaOoLicn4&e=> 2100 Lakeside Blvd, Suite 300 Richardson, TX 75082 USA Recognized 9x in Best Companies to Work for in Texas Technology Training Partner of Mobile World Congress 2017 | More<https://urldefense.proofpoint.com/v2/url?u=http-3A__go.awardsolutions.com_l_147601_2017-2D02-2D07_21z4hn&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=i8UW4Nl4sqUB-rmVcMmBBJdkf488E1p7tjqgRCf-iwc&e=> From: Chris Reece Sent: Tuesday, April 18, 2017 3:21 PM To: 'Ahmad, Munir' <Munir.Ahmad at bell.ca<mailto:Munir.Ahmad at bell.ca>>; Vikram Mukundamgari <vikram.mukundamgari at nexius.com<mailto:vikram.mukundamgari at nexius.com>>; PLATANIA, MARCO (MARCO) <platania at research.att.com<mailto:platania at research.att.com>>; onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> Subject: RE: [onap-discuss] Unable to login as designer role Hello Munir, I ran into the same issue again today. I changed the env file with: - artifacts_version: 1.1.0-SNAPSHOT - docker_version: latest Here is some log info: BE health-Check: { "sdcVersion": "1.1.0", "siteMode": "unknown", "componentsInfo": [ { "healthCheckComponent": "BE", "healthCheckStatus": "UP", "version": "1.1.0", "description": "OK" }, { "healthCheckComponent": "ES", "healthCheckStatus": "UP", "description": "OK" }, { "healthCheckComponent": "TITAN", "healthCheckStatus": "DOWN", "description": "Titan graph is down" }, { "healthCheckComponent": "DE", "healthCheckStatus": "UP", "description": "OK" } ] } Snippet from end of ASDC-BE/error.log 2017-04-18T19:17:24.019Z|||cluster1-reconnection-0||ASDC-BE||ERROR|||11.0.3.10||c.d.driver.core.ControlConnection||ActivityType=<?>, Desc=<[Control connection] Cannot connect to any host, scheduling retry in 1000 milliseconds> 2017-04-18T19:17:24.020Z|||cluster1-reconnection-0||ASDC-BE||ERROR|||11.0.3.10||c.d.driver.core.ControlConnection||ActivityType=<?>, Desc=<[Control connection] Cannot connect to any host, scheduling retry in 30000 milliseconds> 2017-04-18T19:17:25.021Z|||cluster1-reconnection-1||ASDC-BE||ERROR|||11.0.3.10||c.d.driver.core.ControlConnection||ActivityType=<?>, Desc=<[Control connection] Cannot connect to any host, scheduling retry in 2000 milliseconds> ubuntu at vm1-sdc:~$ sudo docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 987eb55c9e78 nexus3.onap.org:10001/openecomp/sdc-frontend:latest "/root/startup.sh" 2 hours ago Up 2 hours 0.0.0.0:8181->8181/tcp, 8080/tcp, 0.0.0.0:9443->9443/tcp sdc-FE aed7d21d3f5f nexus3.onap.org:10001/openecomp/sdc-backend:latest "/root/startup.sh" 2 hours ago Up 2 hours 0.0.0.0:8080->8080/tcp, 0.0.0.0:8443->8443/tcp sdc-BE 2ceadaadd68b nexus3.onap.org:10001/openecomp/sdc-kibana:latest "/root/startup.sh" 2 hours ago Up 2 hours 0.0.0.0:5601->5601/tcp sdc-kbn 4db356603b9e nexus3.onap.org:10001/openecomp/sdc-cassandra:latest "/root/startup.sh" 2 hours ago Up 2 hours 7000-7001/tcp, 0.0.0.0:9042->9042/tcp, 7199/tcp, 0.0.0.0:9160->9160/tcp sdc-cs c6970e5dba47 nexus3.onap.org:10001/openecomp/sdc-elasticsearch:latest "/root/startup.sh" 2 hours ago Up 2 hours 0.0.0.0:9200->9200/tcp, 0.0.0.0:9300->9300/tcp sdc-es I don?t know if they are related, but when SDC stopped working (with the Error Code POL5000), I was not able to connect to VID. I have updated my hosts file. [cid:image018.png at 01D2B9B4.DFA21940] I can connect to DMaaP Bus and Policy, but not xDemo App [cid:image019.png at 01D2B9B4.DFA21940] Anything else you think I should try? Thanks, Chris [cid:image020.png at 01D2B9B4.DFA21940] Chris Reece Technologist www.AwardSolutions.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.awardsolutions.com_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=bs4SWoTyj76sfLy5RIs71-4bw3SXARLFfB8r2JwrOo4&e=> (W) 972-664-0727 x242 | (M) 214-763-9968 [cid:image021.png at 01D2B9B4.DFA21940]<https://urldefense.proofpoint.com/v2/url?u=https-3A__devops2.awardsolutions.com_portal_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=HQ2r3XRpsYTt_tAlvzUSh4QA-c4L5ZrD0gLO2toR0HI&e=>[cid:image022.png at 01D2B9B4.DFA21940]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_company_award-2Dsolutions&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=FMvGOflg1evat6O-PD1lQHXeYK2q6okI0Q0kuS65Q0M&e=>[cid:image023.png at 01D2B9B4.DFA21940]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_awardsolutions&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=F0HrEfG5C2It8RoC07_2VITEt8m2HXC2leQaOoLicn4&e=> 2100 Lakeside Blvd, Suite 300 Richardson, TX 75082 USA Recognized 9x in Best Companies to Work for in Texas Technology Training Partner of Mobile World Congress 2017 | More<https://urldefense.proofpoint.com/v2/url?u=http-3A__go.awardsolutions.com_l_147601_2017-2D02-2D07_21z4hn&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=i8UW4Nl4sqUB-rmVcMmBBJdkf488E1p7tjqgRCf-iwc&e=> From: Ahmad, Munir [mailto:[email protected]] Sent: Tuesday, April 18, 2017 9:40 AM To: Chris Reece <creece at awardsolutions.com<mailto:creece at awardsolutions.com>>; Vikram Mukundamgari <vikram.mukundamgari at nexius.com<mailto:vikram.mukundamgari at nexius.com>>; PLATANIA, MARCO (MARCO) <platania at research.att.com<mailto:platania at research.att.com>>; onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> Subject: Re: [onap-discuss] Unable to login as designer role Chris I noticed you are using 1.0-STAGING-latest we currently have sdc working with latest image as listed below: IMAGE nexus3.openecomp.org:10001/openecomp/sdc-frontend:latest nexus3.openecomp.org:10001/openecomp/sdc-backend:latest nexus3.openecomp.org:10001/openecomp/sdc-kibana:latest nexus3.openecomp.org:10001/openecomp/sdc-cassandra:latest nexus3.openecomp.org:10001/openecomp/sdc-elasticsearch:latest If you review your /var/lib/cloud/instance/user-data.txt file and compare it with below and might be worth rerunning user-data.txt after bringing the changes from below to your user-data.txt #!/bin/bash # DNS/GW IP address configuration mkdir /opt/config echo "10.0.0.1" > /opt/config/dns_gw_ip.txt echo "nameserver 10.0.0.1" >> /etc/resolvconf/resolv.conf.d/head resolvconf -u # Download dependencies add-apt-repository -y ppa:openjdk-r/ppa apt-get update apt-get install -y apt-transport-https ca-certificates wget openjdk-8-jdk ntp ntpdate # Download scripts from Nexus curl -k https://nexus.openecomp.org/content/sites/raw/org.openecomp.demo/boot/1.0.0-SNAPSHOT/asdc_vm_init.sh<https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.openecomp.org_content_sites_raw_org.openecomp.demo_boot_1.0.0-2DSNAPSHOT_asdc-5Fvm-5Finit.sh&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=ScsqbVgXymEf5aiYzmvRNT9_q6nVl0UfvD7I5DQAuSE&e=> -o /opt/asdc_vm_init.sh curl -k https://nexus.openecomp.org/content/sites/raw/org.openecomp.demo/boot/1.0.0-SNAPSHOT/asdc_serv.sh<https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.openecomp.org_content_sites_raw_org.openecomp.demo_boot_1.0.0-2DSNAPSHOT_asdc-5Fserv.sh&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=fpMI9s-WUETBAa7BpytlEmL8p6fY9OoBTfBSWxiRYGs&e=> -o /opt/asdc_serv.sh chmod +x /opt/asdc_vm_init.sh chmod +x /opt/asdc_serv.sh mv /opt/asdc_serv.sh /etc/init.d update-rc.d asdc_serv.sh defaults # Download and install docker-engine and docker-compose apt-key adv --keyserver hkp://ha.pool.sks-keyservers.net:80 --recv-keys removedkey echo "deb https://apt.dockerproject.org/repo<https://urldefense.proofpoint.com/v2/url?u=https-3A__apt.dockerproject.org_repo&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=fVdZsI3NVc0rtok4Xi7Z2VHofr_vARYIjp5L54I69L0&e=> ubuntu-xenial main" | sudo tee /etc/apt/sources.list.d/docker.list apt-get update apt-get install -y linux-image-extra-$(uname -r) linux-image-extra-virtual apt-get install -y docker-engine service docker start mkdir /opt/docker curl -L https://github.com/docker/compose/releases/download/1.9.0/docker-compose-`uname<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_docker_compose_releases_download_1.9.0_docker-2Dcompose-2D-2560uname&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=bSXobbZO121XVB-7ggeAR4fiGN7n4ToS-EmQjR4abbU&e=> -s`-`uname -m` > /opt/docker/docker-compose chmod +x /opt/docker/docker-compose # Create partition and mount the external volume curl -k https://nexus.openecomp.org/content/sites/raw/org.openecomp.demo/boot/1.0.0-SNAPSHOT/asdc_ext_volume_partitions.txt<https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.openecomp.org_content_sites_raw_org.openecomp.demo_boot_1.0.0-2DSNAPSHOT_asdc-5Fext-5Fvolume-5Fpartitions.txt&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=PlTzhR4kh9XJjNQ-q-iIw5HLQ0hpMT5A1mGw9uZCqRc&e=> -o /opt/asdc_ext_volume_partitions.txt sfdisk /dev/xvdb < /opt/asdc_ext_volume_partitions.txt mkfs -t ext4 /dev/xvdb1 mkdir -p /data mount /dev/xvdb1 /data echo "/dev/xvdb1 /data ext4 errors=remount-ro,noatime,barrier=0 0 1" >> /etc/fstab # Store credentials in files mkdir -p /opt/config echo "removeddockerrepo" > /opt/config/nexus_docker_repo.txt echo "removeduser" > /opt/config/nexus_username.txt echo "removedpassword" > /opt/config/nexus_password.txt echo "removeduser" > /opt/config/gitlab_username.txt echo "removedpassword" > /opt/config/gitlab_password.txt echo "AUTO" > /opt/config/env_name.txt # Run SDC-specific instructions cd /opt mkdir -p /data/environments mkdir -p /data/scripts mkdir -p /data/logs/BE mkdir -p /data/logs/FE chmod 777 /data chmod 777 /data/logs/BE chmod 777 /data/logs/FE git clone https://removeduser:removedpassword<https://urldefense.proofpoint.com/v2/url?u=https-3A__removeduser-3Aremovedpassword&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=xyteZ-eBNHwpq5XOMJJFHkG6IIKVndOJywZ3w0zzqG4&e=> @gerrit.openecomp.org/r/a/sdc.git cat > /root/.bash_aliases << EOF alias dcls='/data/scripts/docker_clean.sh \$1' alias dlog='/data/scripts/docker_login.sh \$1' alias rund='/data/scripts/docker_run.sh' alias health='/data/scripts/docker_health.sh' EOF # Run docker-compose to spin up containers ./asdc_vm_init.sh From: Chris Reece <creece at awardsolutions.com<mailto:[email protected]>> Date: Tuesday, April 18, 2017 at 9:21 AM To: "Ahmad, Munir" <Munir.Ahmad at bell.ca<mailto:Munir.Ahmad at bell.ca>>, Vikram Mukundamgari <vikram.mukundamgari at nexius.com<mailto:vikram.mukundamgari at nexius.com>>, "PLATANIA, MARCO (MARCO)" <platania at research.att.com<mailto:platania at research.att.com>>, "onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>" <onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>> Subject: RE: [onap-discuss] Unable to login as designer role Hello Munir, All five of the containers are running and none of them have a ?Exited (1)? status. ubuntu at vm1-sdc:~$ sudo docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 4742d8f053c2 nexus3.onap.org:10001/openecomp/sdc-frontend:1.0-STAGING-latest "/root/startup.sh" 15 hours ago Up 15 hours 0.0.0.0:8181->8181/tcp, 8080/tcp, 0.0.0.0:9443->9443/tcp sdc-FE 690261211f1b nexus3.onap.org:10001/openecomp/sdc-backend:1.0-STAGING-latest "/root/startup.sh" 15 hours ago Up 15 hours 0.0.0.0:8080->8080/tcp, 0.0.0.0:8443->8443/tcp sdc-BE 82db00c45438 nexus3.onap.org:10001/openecomp/sdc-kibana:1.0-STAGING-latest "/root/startup.sh" 15 hours ago Up 15 hours 0.0.0.0:5601->5601/tcp sdc-kbn b041cb031dba nexus3.onap.org:10001/openecomp/sdc-cassandra:1.0-STAGING-latest "/root/startup.sh" 15 hours ago Up 15 hours 7000-7001/tcp, 0.0.0.0:9042->9042/tcp, 7199/tcp, 0.0.0.0:9160->9160/tcp sdc-cs a5ee7ca69d68 nexus3.onap.org:10001/openecomp/sdc-elasticsearch:1.0-STAGING-latest "/root/startup.sh" 15 hours ago Up 15 hours 0.0.0.0:9200->9200/tcp, 0.0.0.0:9300->9300/tcp sdc-es The error this morning I get when I go to SDC is: [cid:image024.png at 01D2B9B4.DFA21940] Let me know if there is anything I can do to help with this issue. Chris [cid:image025.png at 01D2B9B4.DFA21940] Chris Reece Technologist www.AwardSolutions.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.awardsolutions.com_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=bs4SWoTyj76sfLy5RIs71-4bw3SXARLFfB8r2JwrOo4&e=> (W) 972-664-0727 x242 [cid:image026.png at 01D2B9B4.DFA21940]<https://urldefense.proofpoint.com/v2/url?u=https-3A__devops2.awardsolutions.com_portal_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=HQ2r3XRpsYTt_tAlvzUSh4QA-c4L5ZrD0gLO2toR0HI&e=>[cid:image027.png at 01D2B9B4.DFA21940]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_company_award-2Dsolutions&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=FMvGOflg1evat6O-PD1lQHXeYK2q6okI0Q0kuS65Q0M&e=>[cid:image028.png at 01D2B9B4.DFA21940]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_awardsolutions&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=F0HrEfG5C2It8RoC07_2VITEt8m2HXC2leQaOoLicn4&e=> 2100 Lakeside Blvd, Suite 300 Richardson, TX 75082 USA Recognized 9x in Best Companies to Work for in Texas Technology Training Partner of Mobile World Congress 2017 | More<https://urldefense.proofpoint.com/v2/url?u=http-3A__go.awardsolutions.com_l_147601_2017-2D02-2D07_21z4hn&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=i8UW4Nl4sqUB-rmVcMmBBJdkf488E1p7tjqgRCf-iwc&e=> From: Ahmad, Munir [mailto:[email protected]] Sent: Tuesday, April 18, 2017 6:49 AM To: Chris Reece <creece at awardsolutions.com<mailto:creece at awardsolutions.com>>; Vikram Mukundamgari <vikram.mukundamgari at nexius.com<mailto:vikram.mukundamgari at nexius.com>>; PLATANIA, MARCO (MARCO) <platania at research.att.com<mailto:platania at research.att.com>>; onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> Subject: Re: [onap-discuss] Unable to login as designer role Hi Chris/Vikram, Can you run ?sudo docker ps -a? to make sure you have the following five containers running. sdc-FE sdc-BE sdc-kbn sdc-cs sdc-es If you see any of them with status ?Exited (1)? run docker logs for each of the containers with status exited to see what is going on. Thanks Munir From: Chris Reece <creece at awardsolutions.com<mailto:[email protected]>> Date: Monday, April 17, 2017 at 5:57 PM To: "Ahmad, Munir" <Munir.Ahmad at bell.ca<mailto:Munir.Ahmad at bell.ca>>, Vikram Mukundamgari <vikram.mukundamgari at nexius.com<mailto:vikram.mukundamgari at nexius.com>>, "PLATANIA, MARCO (MARCO)" <platania at research.att.com<mailto:platania at research.att.com>>, "onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>" <onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>> Subject: RE: [onap-discuss] Unable to login as designer role Hello Munir, I am having the same issue as Vikram. SDC will work when I first install and about 30 min or so it will give the same error: [cid:image029.png at 01D2B9B4.DFA21940] If I log out and log back into ONAP the error becomes: [cid:image030.png at 01D2B9B4.DFA21940] I ran the healthcheck from below and here is my output: ubuntu at vm1-sdc:~$ curl http://localhost:8181/sdc1/rest/healthCheck<https://urldefense.proofpoint.com/v2/url?u=http-3A__localhost-3A8181_sdc1_rest_healthCheck&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=t9Jdkfukx_zt8_aBh1_RGkMafvoTh6K2K9lNu_P10MA&e=> { "sdcVersion": "1.0.0", "siteMode": "unknown", "componentsInfo": [ { "healthCheckComponent": "BE", "healthCheckStatus": "UP", "version": "1.0.0", "description": "OK" }, { "healthCheckComponent": "ES", "healthCheckStatus": "UP", "description": "OK" }, { "healthCheckComponent": "TITAN", "healthCheckStatus": "DOWN", "description": "Titan graph is down" }, { "healthCheckComponent": "DE", "healthCheckStatus": "UP", "description": "OK" }, { "healthCheckComponent": "FE", "healthCheckStatus": "UP", "version": "1.0.0", "description": "OK" } ] }ubuntu at vm1-sdc:~$ I also ran the ?docker logs sdc-BE? and the results are: [2017-04-17T20:29:32+00:00] INFO: Started chef-zero at chefzero://localhost:8889 with repository at /root/chef-solo One version per cookbook [2017-04-17T20:29:32+00:00] INFO: Forking chef instance to converge... [2017-04-17T20:29:32+00:00] INFO: *** Chef 12.19.36 *** [2017-04-17T20:29:32+00:00] INFO: Platform: x86_64-linux [2017-04-17T20:29:32+00:00] INFO: Chef-client pid: 13 [2017-04-17T20:29:34+00:00] INFO: HTTP Request Returned 404 Not Found: Object not found: chefzero://localhost:8889/nodes/134725a2b66a [2017-04-17T20:29:34+00:00] INFO: Setting the run_list to ["role[catalog-be]"] from CLI options [2017-04-17T20:29:34+00:00] INFO: Run List is [role[catalog-be]] [2017-04-17T20:29:34+00:00] INFO: Run List expands to [sdc-catalog-be::BE_1_cleanup_jettydir, sdc-catalog-be::BE_2_locate_wars, sdc-catalog-be::BE_4_setup_configuration, sdc-catalog-be::BE_5_setup_elasticsearch, sdc-catalog-be::BE_6_setup_portal_properties, sdc-catalog-be::BE_7_logback, sdc-catalog-be::BE_8_errors_config] [2017-04-17T20:29:34+00:00] INFO: Starting Chef Run for 134725a2b66a [2017-04-17T20:29:34+00:00] INFO: Running start handlers [2017-04-17T20:29:34+00:00] INFO: Start handlers complete. [2017-04-17T20:29:34+00:00] INFO: HTTP Request Returned 404 Not Found: Object not found: [2017-04-17T20:29:34+00:00] INFO: Loading cookbooks [sdc-catalog-be at 0.0.0] [2017-04-17T20:29:34+00:00] INFO: Storing updated cookbooks/sdc-catalog-be/recipes/BE_1_cleanup_jettydir.rb in the cache. [2017-04-17T20:29:34+00:00] INFO: Storing updated cookbooks/sdc-catalog-be/recipes/BE_3_create_DMaaP_keys.rb in the cache. [2017-04-17T20:29:34+00:00] INFO: Storing updated cookbooks/sdc-catalog-be/recipes/BE_2_locate_wars.rb in the cache. [2017-04-17T20:29:34+00:00] INFO: Storing updated cookbooks/sdc-catalog-be/recipes/BE_8_errors_config.rb in the cache. [2017-04-17T20:29:34+00:00] INFO: Storing updated cookbooks/sdc-catalog-be/files/default/consumers.py in the cache. [2017-04-17T20:29:34+00:00] INFO: Storing updated cookbooks/sdc-catalog-be/recipes/BE_6_setup_portal_properties.rb in the cache. [2017-04-17T20:29:34+00:00] INFO: Storing updated cookbooks/sdc-catalog-be/recipes/BE_9_import_Normatives.rb in the cache. [2017-04-17T20:29:34+00:00] INFO: Storing updated cookbooks/sdc-catalog-be/recipes/BE_7_logback.rb in the cache. [2017-04-17T20:29:34+00:00] INFO: Storing updated cookbooks/sdc-catalog-be/files/default/BE-ecomp-error-configuration.yaml in the cache. [2017-04-17T20:29:34+00:00] INFO: Storing updated cookbooks/sdc-catalog-be/files/default/BE-error-configuration.yaml in the cache. [2017-04-17T20:29:34+00:00] INFO: Storing updated cookbooks/sdc-catalog-be/files/default/user.py in the cache. [2017-04-17T20:29:34+00:00] INFO: Storing updated cookbooks/sdc-catalog-be/recipes/BE_5_setup_elasticsearch.rb in the cache. [2017-04-17T20:29:34+00:00] INFO: Storing updated cookbooks/sdc-catalog-be/attributes/default.rb in the cache. [2017-04-17T20:29:34+00:00] INFO: Storing updated cookbooks/sdc-catalog-be/recipes/BE_4_setup_configuration.rb in the cache. [2017-04-17T20:29:34+00:00] INFO: Storing updated cookbooks/sdc-catalog-be/templates/default/BE-titan.properties.erb in the cache. [2017-04-17T20:29:34+00:00] INFO: Storing updated cookbooks/sdc-catalog-be/templates/default/BE-portal.properties.erb in the cache. [2017-04-17T20:29:34+00:00] INFO: Storing updated cookbooks/sdc-catalog-be/templates/default/BE-elasticsearch.yml.erb in the cache. [2017-04-17T20:29:34+00:00] INFO: Storing updated cookbooks/sdc-catalog-be/templates/default/BE-configuration.yaml.erb in the cache. [2017-04-17T20:29:34+00:00] INFO: Storing updated cookbooks/sdc-catalog-be/files/default/BE-logback.xml in the cache. [2017-04-17T20:29:34+00:00] INFO: Storing updated cookbooks/sdc-catalog-be/templates/default/BE-distribution-engine-configuration.yaml.erb in the cache. [2017-04-17T20:29:34+00:00] INFO: directory[BE_tempdir_creation] created directory /var/lib/jetty/temp [2017-04-17T20:29:34+00:00] INFO: directory[BE_tempdir_creation] owner changed to 999 [2017-04-17T20:29:34+00:00] INFO: directory[BE_tempdir_creation] group changed to 999 [2017-04-17T20:29:34+00:00] INFO: directory[BE_tempdir_creation] mode changed to 755 [2017-04-17T20:29:34+00:00] INFO: directory[BE_create_config_dir] created directory /var/lib/jetty/config [2017-04-17T20:29:34+00:00] INFO: directory[BE_create_config_dir] owner changed to 999 [2017-04-17T20:29:34+00:00] INFO: directory[BE_create_config_dir] group changed to 999 [2017-04-17T20:29:34+00:00] INFO: directory[BE_create_config_dir] mode changed to 755 [2017-04-17T20:29:34+00:00] INFO: directory[BE_create_catalog-be] created directory /var/lib/jetty/config/catalog-be [2017-04-17T20:29:34+00:00] INFO: directory[BE_create_catalog-be] owner changed to 999 [2017-04-17T20:29:34+00:00] INFO: directory[BE_create_catalog-be] group changed to 999 [2017-04-17T20:29:34+00:00] INFO: directory[BE_create_catalog-be] mode changed to 755 [2017-04-17T20:29:35+00:00] INFO: bash[create-jetty-modules] ran successfully [2017-04-17T20:29:35+00:00] INFO: template[titan.properties] created file /var/lib/jetty/config/catalog-be/titan.properties [2017-04-17T20:29:35+00:00] INFO: template[titan.properties] updated file contents /var/lib/jetty/config/catalog-be/titan.properties [2017-04-17T20:29:35+00:00] INFO: template[titan.properties] owner changed to 999 [2017-04-17T20:29:35+00:00] INFO: template[titan.properties] group changed to 999 [2017-04-17T20:29:35+00:00] INFO: template[titan.properties] mode changed to 755 [2017-04-17T20:29:35+00:00] INFO: template[catalog-be-config] created file /var/lib/jetty/config/catalog-be/configuration.yaml [2017-04-17T20:29:35+00:00] INFO: template[catalog-be-config] updated file contents /var/lib/jetty/config/catalog-be/configuration.yaml [2017-04-17T20:29:35+00:00] INFO: template[catalog-be-config] owner changed to 999 [2017-04-17T20:29:35+00:00] INFO: template[catalog-be-config] group changed to 999 [2017-04-17T20:29:35+00:00] INFO: template[catalog-be-config] mode changed to 755 [2017-04-17T20:29:35+00:00] INFO: template[distribution-engine-configuration] created file /var/lib/jetty/config/catalog-be/distribution-engine-configuration.yaml [2017-04-17T20:29:35+00:00] INFO: template[distribution-engine-configuration] updated file contents /var/lib/jetty/config/catalog-be/distribution-engine-configuration.yaml [2017-04-17T20:29:35+00:00] INFO: template[distribution-engine-configuration] owner changed to 999 [2017-04-17T20:29:35+00:00] INFO: template[distribution-engine-configuration] group changed to 999 [2017-04-17T20:29:35+00:00] INFO: template[distribution-engine-configuration] mode changed to 755 [2017-04-17T20:29:35+00:00] INFO: template[elasticsearch.yml-config] created file /var/lib/jetty/config/elasticsearch.yml [2017-04-17T20:29:35+00:00] INFO: template[elasticsearch.yml-config] updated file contents /var/lib/jetty/config/elasticsearch.yml [2017-04-17T20:29:35+00:00] INFO: template[elasticsearch.yml-config] owner changed to 999 [2017-04-17T20:29:35+00:00] INFO: template[elasticsearch.yml-config] group changed to 999 [2017-04-17T20:29:35+00:00] INFO: template[elasticsearch.yml-config] mode changed to 755 [2017-04-17T20:29:35+00:00] INFO: template[template portal.properties] created file /var/lib/jetty/resources/portal.properties [2017-04-17T20:29:35+00:00] INFO: template[template portal.properties] updated file contents /var/lib/jetty/resources/portal.properties [2017-04-17T20:29:35+00:00] INFO: template[template portal.properties] owner changed to 999 [2017-04-17T20:29:35+00:00] INFO: template[template portal.properties] group changed to 999 [2017-04-17T20:29:35+00:00] INFO: template[template portal.properties] mode changed to 755 [2017-04-17T20:29:35+00:00] INFO: cookbook_file[/var/lib/jetty/config/catalog-be/logback.xml] created file /var/lib/jetty/config/catalog-be/logback.xml [2017-04-17T20:29:35+00:00] INFO: cookbook_file[/var/lib/jetty/config/catalog-be/logback.xml] updated file contents /var/lib/jetty/config/catalog-be/logback.xml [2017-04-17T20:29:35+00:00] INFO: cookbook_file[/var/lib/jetty/config/catalog-be/logback.xml] owner changed to 999 [2017-04-17T20:29:35+00:00] INFO: cookbook_file[/var/lib/jetty/config/catalog-be/logback.xml] group changed to 999 [2017-04-17T20:29:35+00:00] INFO: cookbook_file[/var/lib/jetty/config/catalog-be/logback.xml] mode changed to 755 [2017-04-17T20:29:35+00:00] INFO: cookbook_file[/var/lib/jetty/config/catalog-be/ecomp-error-configuration.yaml] created file /var/lib/jetty/config/catalog-be/ecomp-error-configuration.yaml [2017-04-17T20:29:35+00:00] INFO: cookbook_file[/var/lib/jetty/config/catalog-be/ecomp-error-configuration.yaml] updated file contents /var/lib/jetty/config/catalog-be/ecomp-error-configuration.yaml [2017-04-17T20:29:35+00:00] INFO: cookbook_file[/var/lib/jetty/config/catalog-be/ecomp-error-configuration.yaml] owner changed to 999 [2017-04-17T20:29:35+00:00] INFO: cookbook_file[/var/lib/jetty/config/catalog-be/ecomp-error-configuration.yaml] group changed to 999 [2017-04-17T20:29:35+00:00] INFO: cookbook_file[/var/lib/jetty/config/catalog-be/ecomp-error-configuration.yaml] mode changed to 755 [2017-04-17T20:29:35+00:00] INFO: cookbook_file[/var/lib/jetty/config/catalog-be/error-configuration.yaml] created file /var/lib/jetty/config/catalog-be/error-configuration.yaml [2017-04-17T20:29:35+00:00] INFO: cookbook_file[/var/lib/jetty/config/catalog-be/error-configuration.yaml] updated file contents /var/lib/jetty/config/catalog-be/error-configuration.yaml [2017-04-17T20:29:35+00:00] INFO: cookbook_file[/var/lib/jetty/config/catalog-be/error-configuration.yaml] owner changed to 999 [2017-04-17T20:29:35+00:00] INFO: cookbook_file[/var/lib/jetty/config/catalog-be/error-configuration.yaml] group changed to 999 [2017-04-17T20:29:35+00:00] INFO: cookbook_file[/var/lib/jetty/config/catalog-be/error-configuration.yaml] mode changed to 755 [2017-04-17T20:29:35+00:00] INFO: Chef Run complete in 1.39608927 seconds [2017-04-17T20:29:35+00:00] INFO: Running report handlers [2017-04-17T20:29:35+00:00] INFO: Report handlers complete [ERROR]: 2017/04/17 20:29:35 Backend not responding, try #1 [INFO]: Backend is up and running [ERROR]: 2017/04/17 20:29:35 Backend not responding, try #1 [INFO]: Backend is up and running [INFO] create first:[demo], last:[demo], Id:[demo], email:[demo at openecomp.org], role:[ADMIN] [INFO]: demo created, result: [201] [2017-04-17T20:30:16+00:00] INFO: Started chef-zero at chefzero://localhost:8889 with repository at /root/chef-solo One version per cookbook [2017-04-17T20:30:16+00:00] INFO: Forking chef instance to converge... [2017-04-17T20:30:16+00:00] INFO: *** Chef 12.19.36 *** [2017-04-17T20:30:16+00:00] INFO: Platform: x86_64-linux [2017-04-17T20:30:16+00:00] INFO: Chef-client pid: 487 [2017-04-17T20:30:17+00:00] INFO: Setting the run_list to ["recipe[sdc-normatives::import_Normatives]"] from CLI options [2017-04-17T20:30:17+00:00] INFO: Run List is [recipe[sdc-normatives::import_Normatives]] [2017-04-17T20:30:17+00:00] INFO: Run List expands to [sdc-normatives::import_Normatives] [2017-04-17T20:30:17+00:00] INFO: Starting Chef Run for 134725a2b66a [2017-04-17T20:30:17+00:00] INFO: Running start handlers [2017-04-17T20:30:17+00:00] INFO: Start handlers complete. [2017-04-17T20:30:17+00:00] INFO: HTTP Request Returned 404 Not Found: Object not found: [2017-04-17T20:30:17+00:00] INFO: Loading cookbooks [sdc-normatives at 0.0.0] [2017-04-17T20:30:17+00:00] INFO: Removing cookbooks/sdc-catalog-be/recipes/BE_7_logback.rb from the cache; its cookbook is no longer needed on this client. [2017-04-17T20:30:17+00:00] INFO: Removing cookbooks/sdc-catalog-be/recipes/BE_2_locate_wars.rb from the cache; its cookbook is no longer needed on this client. [2017-04-17T20:30:17+00:00] INFO: Removing cookbooks/sdc-catalog-be/recipes/BE_9_import_Normatives.rb from the cache; its cookbook is no longer needed on this client. [2017-04-17T20:30:17+00:00] INFO: Removing cookbooks/sdc-catalog-be/recipes/BE_1_cleanup_jettydir.rb from the cache; its cookbook is no longer needed on this client. [2017-04-17T20:30:17+00:00] INFO: Removing cookbooks/sdc-catalog-be/recipes/BE_4_setup_configuration.rb from the cache; its cookbook is no longer needed on this client. [2017-04-17T20:30:17+00:00] INFO: Removing cookbooks/sdc-catalog-be/recipes/BE_5_setup_elasticsearch.rb from the cache; its cookbook is no longer needed on this client. [2017-04-17T20:30:17+00:00] INFO: Removing cookbooks/sdc-catalog-be/recipes/BE_6_setup_portal_properties.rb from the cache; its cookbook is no longer needed on this client. [2017-04-17T20:30:17+00:00] INFO: Removing cookbooks/sdc-catalog-be/recipes/BE_8_errors_config.rb from the cache; its cookbook is no longer needed on this client. [2017-04-17T20:30:17+00:00] INFO: Removing cookbooks/sdc-catalog-be/recipes/BE_3_create_DMaaP_keys.rb from the cache; its cookbook is no longer needed on this client. [2017-04-17T20:30:17+00:00] INFO: Removing cookbooks/sdc-catalog-be/files/default/BE-logback.xml from the cache; its cookbook is no longer needed on this client. [2017-04-17T20:30:17+00:00] INFO: Removing cookbooks/sdc-catalog-be/files/default/user.py from the cache; its cookbook is no longer needed on this client. [2017-04-17T20:30:17+00:00] INFO: Removing cookbooks/sdc-catalog-be/files/default/BE-error-configuration.yaml from the cache; its cookbook is no longer needed on this client. [2017-04-17T20:30:17+00:00] INFO: Removing cookbooks/sdc-catalog-be/files/default/consumers.py from the cache; its cookbook is no longer needed on this client. [2017-04-17T20:30:17+00:00] INFO: Removing cookbooks/sdc-catalog-be/files/default/BE-ecomp-error-configuration.yaml from the cache; its cookbook is no longer needed on this client. [2017-04-17T20:30:17+00:00] INFO: Removing cookbooks/sdc-catalog-be/templates/default/BE-configuration.yaml.erb from the cache; its cookbook is no longer needed on this client. [2017-04-17T20:30:17+00:00] INFO: Removing cookbooks/sdc-catalog-be/templates/default/BE-elasticsearch.yml.erb from the cache; its cookbook is no longer needed on this client. [2017-04-17T20:30:17+00:00] INFO: Removing cookbooks/sdc-catalog-be/templates/default/BE-portal.properties.erb from the cache; its cookbook is no longer needed on this client. [2017-04-17T20:30:17+00:00] INFO: Removing cookbooks/sdc-catalog-be/templates/default/BE-titan.properties.erb from the cache; its cookbook is no longer needed on this client. [2017-04-17T20:30:17+00:00] INFO: Removing cookbooks/sdc-catalog-be/templates/default/BE-distribution-engine-configuration.yaml.erb from the cache; its cookbook is no longer needed on this client. [2017-04-17T20:30:17+00:00] INFO: Removing cookbooks/sdc-catalog-be/attributes/default.rb from the cache; its cookbook is no longer needed on this client. [2017-04-17T20:30:17+00:00] INFO: Storing updated cookbooks/sdc-normatives/recipes/check_Backend.rb in the cache. [2017-04-17T20:30:17+00:00] INFO: Storing updated cookbooks/sdc-normatives/recipes/import_Normatives.rb in the cache. [2017-04-17T20:30:17+00:00] INFO: Storing updated cookbooks/sdc-normatives/files/default/check_Backend_Health.py in the cache. [2017-04-17T20:30:17+00:00] INFO: Storing updated cookbooks/sdc-normatives/attributes/default.rb in the cache. [2017-04-17T20:30:17+00:00] INFO: Storing updated cookbooks/sdc-normatives/recipes/upgrade_Normatives.rb in the cache. [2017-04-17T20:30:17+00:00] INFO: Storing updated cookbooks/sdc-normatives/files/default/normatives.tar.gz in the cache. [2017-04-17T20:30:17+00:00] INFO: Storing updated cookbooks/sdc-normatives/files/default/get-pip.py in the cache. [2017-04-17T20:30:17+00:00] INFO: cookbook_file[/tmp/normatives.tar.gz] created file /tmp/normatives.tar.gz [2017-04-17T20:30:17+00:00] INFO: cookbook_file[/tmp/normatives.tar.gz] updated file contents /tmp/normatives.tar.gz [ERROR]: 2017/04/17 20:29:35 Backend not responding, try #1 [INFO]: Backend is up and running [INFO] aai [INFO]: aai created, result: [201] [INFO] appc [INFO]: appc created, result: [201] [INFO] dcae [INFO]: dcae created, result: [201] [INFO] mso [INFO]: mso created, result: [201] [INFO] sdnc [INFO]: sdnc created, result: [201] [INFO] vid [INFO]: vid created, result: [201] [2017-04-17T20:33:59+00:00] INFO: bash[import-normatives] ran successfully [2017-04-17T20:33:59+00:00] INFO: Chef Run complete in 222.047278784 seconds [2017-04-17T20:33:59+00:00] INFO: Running report handlers [2017-04-17T20:33:59+00:00] INFO: Report handlers complete Ifconfig: docker0 Link encap:Ethernet HWaddr 02:42:b1:23:00:18 inet addr:172.17.0.1 Bcast:0.0.0.0 Mask:255.255.0.0 inet6 addr: fe80::42:b1ff:fe23:18/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:186409 errors:0 dropped:0 overruns:0 frame:0 TX packets:186047 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:48006637 (48.0 MB) TX bytes:47908482 (47.9 MB) eth0 Link encap:Ethernet HWaddr fa:16:3e:d6:21:07 inet addr:11.0.3.10 Bcast:11.255.255.255 Mask:255.0.0.0 inet6 addr: fe80::f816:3eff:fed6:2107/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:700088 errors:0 dropped:0 overruns:0 frame:0 TX packets:599108 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1445873455 (1.4 GB) TX bytes:76818641 (76.8 MB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:90 errors:0 dropped:0 overruns:0 frame:0 TX packets:90 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:12205 (12.2 KB) TX bytes:12205 (12.2 KB) veth031b8c1 Link encap:Ethernet HWaddr 86:f7:bd:9e:95:88 inet6 addr: fe80::84f7:bdff:fe9e:9588/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:135284 errors:0 dropped:0 overruns:0 frame:0 TX packets:132044 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:31999785 (31.9 MB) TX bytes:36422345 (36.4 MB) veth038a2fb Link encap:Ethernet HWaddr de:a7:f4:ed:bf:b6 inet6 addr: fe80::dca7:f4ff:feed:bfb6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:44885 errors:0 dropped:0 overruns:0 frame:0 TX packets:56305 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:20885553 (20.8 MB) TX bytes:14961731 (14.9 MB) veth27b5507 Link encap:Ethernet HWaddr d6:57:61:4c:e3:22 inet6 addr: fe80::d457:61ff:fe4c:e322/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:49821 errors:0 dropped:0 overruns:0 frame:0 TX packets:33779 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4358044 (4.3 MB) TX bytes:10990206 (10.9 MB) veth53db0f0 Link encap:Ethernet HWaddr d6:0b:6e:4a:df:81 inet6 addr: fe80::d40b:6eff:fe4a:df81/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:30100 errors:0 dropped:0 overruns:0 frame:0 TX packets:39237 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:9997917 (9.9 MB) TX bytes:4904404 (4.9 MB) vethe0a47aa Link encap:Ethernet HWaddr b6:d7:e5:a1:81:a6 inet6 addr: fe80::b4d7:e5ff:fea1:81a6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8817 errors:0 dropped:0 overruns:0 frame:0 TX packets:7239 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4669597 (4.6 MB) TX bytes:1928559 (1.9 MB) I get the following in the /data/logs/BE/ASDC/ASDC-BE/error.log: 2017-04-17T21:19:05.199Z|||cluster1-reconnection-0||ASDC-BE||ERROR|||11.0.3.10||c.d.driver.core.ControlConnection||ActivityType=<?>, Desc=<[Control connection] Cannot connect to any host, scheduling retry in 30000 milliseconds> 2017-04-17T21:19:05.199Z|||cluster1-reconnection-0||ASDC-BE||ERROR|||11.0.3.10||c.d.driver.core.ControlConnection||ActivityType=<?>, Desc=<[Control connection] Cannot connect to any host, scheduling retry i I was having this issue earlier today and the logs implied there was a networking issue between ASDC-FE and ASDC-BE that ASDC-BE failed. I reinstalled ONAP to see if I could reproduce the issue. Here are the logs from earlier today: Let me know if there is anything else I can do to help debug this issue. Thanks, Chris [cid:image031.png at 01D2B9B4.DFA21940] Chris Reece Technologist www.AwardSolutions.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.awardsolutions.com_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=bs4SWoTyj76sfLy5RIs71-4bw3SXARLFfB8r2JwrOo4&e=> (W) 972-664-0727 x242 [cid:image032.png at 01D2B9B4.DFA21940]<https://urldefense.proofpoint.com/v2/url?u=https-3A__devops2.awardsolutions.com_portal_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=HQ2r3XRpsYTt_tAlvzUSh4QA-c4L5ZrD0gLO2toR0HI&e=>[cid:image033.png at 01D2B9B4.DFA21940]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_company_award-2Dsolutions&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=FMvGOflg1evat6O-PD1lQHXeYK2q6okI0Q0kuS65Q0M&e=>[cid:image034.png at 01D2B9B4.DFA21940]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_awardsolutions&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=F0HrEfG5C2It8RoC07_2VITEt8m2HXC2leQaOoLicn4&e=> 2100 Lakeside Blvd, Suite 300 Richardson, TX 75082 USA Recognized 9x in Best Companies to Work for in Texas Technology Training Partner of Mobile World Congress 2017 | More<https://urldefense.proofpoint.com/v2/url?u=http-3A__go.awardsolutions.com_l_147601_2017-2D02-2D07_21z4hn&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=i8UW4Nl4sqUB-rmVcMmBBJdkf488E1p7tjqgRCf-iwc&e=> From: onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at lists.onap.org> [mailto:[email protected]] On Behalf Of Ahmad, Munir Sent: Monday, April 17, 2017 4:34 PM To: Vikram Mukundamgari <vikram.mukundamgari at nexius.com<mailto:vikram.mukundamgari at nexius.com>>; PLATANIA, MARCO (MARCO) <platania at research.att.com<mailto:platania at research.att.com>>; onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org> Subject: Re: [onap-discuss] Unable to login as designer role Hi Vikram, This can be because of you sdc backend container is not running correctly? you should have all of the following containers in your sdc vm: root at vm1-sdc:~# curl http://localhost:8181/sdc1/rest/healthCheck<https://urldefense.proofpoint.com/v2/url?u=http-3A__localhost-3A8181_sdc1_rest_healthCheck&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=AODV_JEO9Y482LV1fZomadFRSu7Jal1SsSpgk2PusJw&s=t9Jdkfukx_zt8_aBh1_RGkMafvoTh6K2K9lNu_P10MA&e=> { "sdcVersion": "1.1.0", "siteMode": "unknown", "componentsInfo": [ { "healthCheckComponent": "BE", "healthCheckStatus": "UP", "version": "1.1.0", "description": "OK" }, { "healthCheckComponent": "ES", "healthCheckStatus": "UP", "description": "OK" }, { "healthCheckComponent": "TITAN", "healthCheckStatus": "UP", "description": "OK" }, { "healthCheckComponent": "DE", "healthCheckStatus": "DOWN", "description": "U-EB cluster is not available" }, { "healthCheckComponent": "FE", "healthCheckStatus": "UP", "version": "1.1.0", "description": "OK" } ] }root at vm1-sdc:~# to further investigate this please run ?docker logs sdc-BE? if you see any errors next check if your interface names are correct. }root at vm1-sdc:~# ifconfig eth0 Link encap:Ethernet HWaddr fa:16:3e:b4:7a:5e inet addr:10.0.3.1 Bcast:10.255.255.255 Mask:255.0.0.0 inet6 addr: fe80::f816:3eff:feb4:7a5e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1450 Metric:1 RX packets:1065298 errors:0 dropped:0 overruns:0 frame:0 TX packets:523246 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:77563355 (77.5 MB) TX bytes:49167009 (49.1 MB) eth1 Link encap:Ethernet HWaddr fa:16:3e:2b:5b:3f inet addr:192.168.2.76 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: fe80::f816:3eff:fe2b:5b3f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:814097 errors:0 dropped:0 overruns:0 frame:0 TX packets:852936 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:976319221 (976.3 MB) TX bytes:197408952 (197.4 MB) If you do not have the above two interfaces then you need to rename the following two interfaces. ? ens4 to eth0 ? ens3 to eth1 then rerun the /var/lib/cloud/instance/user-data.txt From: <onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at lists.onap.org>> on behalf of Vikram Mukundamgari <vikram.mukundamgari at nexius.com<mailto:[email protected]>> Date: Monday, April 17, 2017 at 5:16 PM To: "PLATANIA, MARCO (MARCO)" <platania at research.att.com<mailto:platania at research.att.com>>, "onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>" <onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>> Subject: Re: [onap-discuss] Unable to login as designer role Hi , I was able to login as designer after running the command mentioned below But I am getting an internal server error after I click SDC icon . Attached is the screenshot of the error . Thanks, Vikram From: "PLATANIA, MARCO (MARCO)" <platania at research.att.com<mailto:[email protected]>> Date: Wednesday, April 12, 2017 at 1:58 PM To: Vikram Mukundamgari <vikram.mukundamgari at nexius.com<mailto:vikram.mukundamgari at nexius.com>>, "onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>" <onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>> Cc: "TALASILA, MANOOP (MANOOP)" <talasila at research.att.com<mailto:talasila at research.att.com>> Subject: Re: [onap-discuss] Unable to login as designer role Vikram, Could you please run these operations? Try to login again as superuser (demo/demo123456!) and see if applications like VID, SDC and Policy appear in the Portal (assuming that you correctly configured your /etc/hosts file, as described in the wiki). If you don?t see any applications in the Portal's home page, then it could be that the users.sql script did not get executed during deployment. This would explain your access issues. If so, try to run: mysql -u root -p'Aa123456' -h $IP_ADDRESS < /opt/portal/deliveries/Apps_Users_OnBoarding_Script.sql where IP_ADDRESS is the public IP address of the Portal VM. Then, try to login again as cs0008. Thanks, Marco From: Vikram Mukundamgari <vikram.mukundamgari at nexius.com<mailto:[email protected]>> Date: Wednesday, April 12, 2017 at 2:59 PM To: "PLATANIA, MARCO (MARCO)" <platania at research.att.com<mailto:platania at research.att.com>>, "onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>" <onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>> Subject: Re: [onap-discuss] Unable to login as designer role Hi Marco, Thank you for the reply, Yes, I was able to login using demo/demo123456! But failed when I tried cs0008/demo123456! as mentioned in https://wiki.onap.org/display/DW/Creating+a+Licensing+Model<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Creating-2Ba-2BLicensing-2BModel&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=A4ZSUd8UW84z64_htLsU7JWnKkPC1GvQm5xaZoaodZ0&s=mjV86nbvORA8OGCw35Ob1Bj-BCDS42GO5xT1mVgWtRA&e=> Thanks, Vikram From: "PLATANIA, MARCO (MARCO)" <platania at research.att.com<mailto:[email protected]>> Date: Wednesday, April 12, 2017 at 11:20 AM To: Vikram Mukundamgari <vikram.mukundamgari at nexius.com<mailto:vikram.mukundamgari at nexius.com>>, "onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>" <onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>> Subject: Re: [onap-discuss] Unable to login as designer role Hello Vikram, Have you tried to login with the superuser: demo/demo123456! ? Please let us know if that works. Thanks, Marco From: <onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at lists.onap.org>> on behalf of Vikram Mukundamgari <vikram.mukundamgari at nexius.com<mailto:[email protected]>> Date: Wednesday, April 12, 2017 at 2:05 PM To: "onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>" <onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>> Subject: [onap-discuss] Unable to login as designer role Hi All, I created a ONAP-Demo stack on Openstack-Mitaka using the heat templates provided in wiki.onap.org. I am unable to login as designer role with user id cs0008 and password demo123456! Can anyone help me with the logging issues Thanks Vikram -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10066 bytes Desc: image001.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0034.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 4248 bytes Desc: image002.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0035.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 4184 bytes Desc: image003.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0036.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 4280 bytes Desc: image004.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0037.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 39215 bytes Desc: image005.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0038.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 9977 bytes Desc: image006.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0039.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.png Type: image/png Size: 4085 bytes Desc: image007.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0040.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image008.png Type: image/png Size: 4060 bytes Desc: image008.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0041.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image009.png Type: image/png Size: 4182 bytes Desc: image009.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0042.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image010.png Type: image/png Size: 9977 bytes Desc: image010.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0043.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image011.png Type: image/png Size: 4085 bytes Desc: image011.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0044.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image012.png Type: image/png Size: 4060 bytes Desc: image012.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0045.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image013.png Type: image/png Size: 4182 bytes Desc: image013.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0046.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image014.png Type: image/png Size: 9918 bytes Desc: image014.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0047.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image015.png Type: image/png Size: 4010 bytes Desc: image015.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0048.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image016.png Type: image/png Size: 3964 bytes Desc: image016.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0049.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image017.png Type: image/png Size: 4078 bytes Desc: image017.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0050.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image018.png Type: image/png Size: 18894 bytes Desc: image018.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0051.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image019.png Type: image/png Size: 74403 bytes Desc: image019.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0052.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image020.png Type: image/png Size: 9909 bytes Desc: image020.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0053.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image021.png Type: image/png Size: 3910 bytes Desc: image021.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0054.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image022.png Type: image/png Size: 3861 bytes Desc: image022.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0055.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image023.png Type: image/png Size: 3968 bytes Desc: image023.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0056.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image024.png Type: image/png Size: 22175 bytes Desc: image024.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0057.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image025.png Type: image/png Size: 9876 bytes Desc: image025.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0058.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image026.png Type: image/png Size: 3818 bytes Desc: image026.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0059.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image027.png Type: image/png Size: 3774 bytes Desc: image027.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0060.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image028.png Type: image/png Size: 3877 bytes Desc: image028.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0061.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image029.png Type: image/png Size: 31913 bytes Desc: image029.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0062.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image030.png Type: image/png Size: 52231 bytes Desc: image030.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0063.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image031.png Type: image/png Size: 9725 bytes Desc: image031.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0064.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image032.png Type: image/png Size: 3573 bytes Desc: image032.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0065.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image033.png Type: image/png Size: 3526 bytes Desc: image033.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0066.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image034.png Type: image/png Size: 3643 bytes Desc: image034.png URL: <http://lists.onap.org/pipermail/onap-discuss/attachments/20170420/32831075/attachment-0067.png>
