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> on behalf of Vikram Mukundamgari 
<[email protected]>
Date: Monday, April 17, 2017 at 5:16 PM
To: "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

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)" <[email protected]>
Date: Wednesday, April 12, 2017 at 1:58 PM
To: Vikram Mukundamgari <vikram.mukundamgari at nexius.com>, "onap-discuss at 
lists.onap.org" <onap-discuss at lists.onap.org>
Cc: "TALASILA, MANOOP (MANOOP)" <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 <[email protected]>
Date: Wednesday, April 12, 2017 at 2:59 PM
To: "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

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)" <[email protected]>
Date: Wednesday, April 12, 2017 at 11:20 AM
To: Vikram Mukundamgari <vikram.mukundamgari at nexius.com>, "onap-discuss at 
lists.onap.org" <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> on behalf of Vikram Mukundamgari 
<[email protected]>
Date: Wednesday, April 12, 2017 at 2:05 PM
To: "onap-discuss at lists.onap.org" <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/20170417/7b1c5763/attachment-0001.html>

Reply via email to