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
 -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
 -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 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 
-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
 -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 @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 <cre...@awardsolutions.com>
Date: Tuesday, April 18, 2017 at 9:21 AM
To: "Ahmad, Munir" <Munir.Ahmad at bell.ca>, Vikram Mukundamgari 
<vikram.mukundamgari at nexius.com>, "PLATANIA, MARCO (MARCO)" <platania at 
research.att.com>, "onap-discuss at lists.onap.org" <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:image001.png at 01D2B830.231A1AA0]

Let me know if there is anything I can do to help with this issue.

Chris

[id:image001.png at 01D1F3C0.B46A49B0]

Chris Reece
Technologist

www.AwardSolutions.com<http://www.awardsolutions.com/>

(W) 972-664-0727 x242

[id:image003.png at 
01D1F3D6.75565C80]<https://devops2.awardsolutions.com/portal/>[id:image005.png 
at 
01D1F3D6.75565C80]<https://www.linkedin.com/company/award-solutions>[id:image007.png
 at 01D1F3D6.75565C80]<https://twitter.com/awardsolutions>

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<http://go.awardsolutions.com/l/147601/2017-02-07/21z4hn>

From: Ahmad, Munir [mailto:munir.ah...@bell.ca]
Sent: Tuesday, April 18, 2017 6:49 AM
To: Chris Reece <creece at awardsolutions.com>; Vikram Mukundamgari 
<vikram.mukundamgari at nexius.com>; PLATANIA, MARCO (MARCO) <platania at 
research.att.com>; 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:cre...@awardsolutions.com>>
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:image006.png at 01D2B830.231A1AA0]

If I log out and log back into ONAP the error becomes:
[cid:image007.png at 01D2B830.231A1AA0]

I ran the healthcheck from below and here is my output:

ubuntu at vm1-sdc:~$ curl http://localhost:8181/sdc1/rest/healthCheck
{
  "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:image008.png at 01D2B830.231A1AA0]

Chris Reece
Technologist

www.AwardSolutions.com<http://www.awardsolutions.com/>

(W) 972-664-0727 x242

[cid:image009.png at 
01D2B830.231A1AA0]<https://devops2.awardsolutions.com/portal/>[cid:image010.png 
at 
01D2B830.231A1AA0]<https://www.linkedin.com/company/award-solutions>[cid:image011.png
 at 01D2B830.231A1AA0]<https://twitter.com/awardsolutions>

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<http://go.awardsolutions.com/l/147601/2017-02-07/21z4hn>

From: onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at 
lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] 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
{
  "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:vikram.mukundamg...@nexius.com>>
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:plata...@research.att.com>>
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:vikram.mukundamg...@nexius.com>>
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:plata...@research.att.com>>
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:vikram.mukundamg...@nexius.com>>
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/20170418/60eb0e65/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 11895 bytes
Desc: image001.png
URL: 
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170418/60eb0e65/attachment-0011.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 2327 bytes
Desc: image002.png
URL: 
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170418/60eb0e65/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 2990 bytes
Desc: image003.png
URL: 
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170418/60eb0e65/attachment-0013.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 2772 bytes
Desc: image004.png
URL: 
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170418/60eb0e65/attachment-0014.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 2837 bytes
Desc: image005.png
URL: 
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170418/60eb0e65/attachment-0015.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 13822 bytes
Desc: image006.png
URL: 
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170418/60eb0e65/attachment-0016.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 24239 bytes
Desc: image007.png
URL: 
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170418/60eb0e65/attachment-0017.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 2328 bytes
Desc: image008.png
URL: 
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170418/60eb0e65/attachment-0018.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 2991 bytes
Desc: image009.png
URL: 
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170418/60eb0e65/attachment-0019.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.png
Type: image/png
Size: 2773 bytes
Desc: image010.png
URL: 
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170418/60eb0e65/attachment-0020.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image011.png
Type: image/png
Size: 2838 bytes
Desc: image011.png
URL: 
<http://lists.onap.org/pipermail/onap-discuss/attachments/20170418/60eb0e65/attachment-0021.png>

Reply via email to