Controller UI page is not loading/accessable,,,

[SatishK]

Good day,

I am not able to access the controller UI,

When I enter the  https://controller_ip_address:8443/sdn/ui/ (where the IP address is the address of server, where I have installed controller), I am not able to access it.

I get the error as Unable to connect. Using Firefox browser in the server.

Regards,

Satish K

[sdnindia]

Hello Satish,

Please provide/confirm the below details-

1. Did you install the version 2.3 a fresh or upgrade from older version?

2. What is the keystone version?

3. Command used to install keystone?

4. Are you able to see REST API page?

5. Did you try with Google chrome ? Chrome is recommended.

6.Please share the screen shot for SDN UI page as well as controller logs if possible.

Thanks,

HP SDN Team

[SatishK]

Hi,

Thanks for the update,

Please find the details below

1. Did you install the version 2.3 a fresh or upgrade from older version?
Yes, I Did a fresh installation of 2.3

2. What is the keystone version?

$keystone --version
0.7.1 (Icehouse)

3. Command used to install keystone?
$ sudo add-apt-repository "deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/icehouse main"
$ sudo apt-get install keystone

4. Are you able to see REST API page?
Do you mean Controller api page ? https://controller-IP:8443/api
then No, I am not able to access this page too.

5. Did you try with Google chrome ? Chrome is recommended.
I dint tried with crome, I am not able to install crome in my server due to proxy restriction.
When I tried to install chrome it says refusing by the proxy server.

6.Please share the screen shot for SDN UI page as well as controller logs if possible.
I have shared the screenshot, for logs I will do, as they are at the servers.

Also please note that,

the same prob with https://<controller_IP>:8443/sdn/v2.0/models

I can able to ping to the controller, from its terminal.

Regards,

Satish K

[SatishK]

Hi Team,

Looks like nothing is listening on 8443.

as per the attached 

[EricAtHP]

Hi Satish,

I have seen this before. I am not entirely sure what causes it. In my case, I think it was a misconfiguration or corruption in keystone. I uninstalled the controller and keystone and reinstalled. 

Keep in mind that with the icehouse version of keystone, you have to edit the /etc/keystone/keystone.conf file for it to work with the VAN SDN Controller. Edit the file and search for "providers". Then add/edit the line below to look like this:

provider=keystone.token.providers.uuid.Provider

Then restart the keystone service. Finally install version 2.3 of the controller.

You will also have to add a user to keystone since one is not added by default anymore. Here are the commands I use to do it:

export OS_SERVICE_TOKEN=ADMIN
export OS_SERVICE_ENDPOINT=http://127.0.0.1:35357/v2.0
keystone user-create --name sdn
keystone role-create --name sdn-admin
keystone role-create --name sdn-user
keystone tenant-create --name sdn
keystone user-role-add --user <user-id> --role <role-id> --tenant_id <tenant-id>
keystone user-password-update --pass skyline <user-id>

The placeholders in "<>" are replaced by the id output of the previous commands. You can run this command to verify the configuration:

keystone user-role-list --user <user-id> --tenant <tenant-id>

[SatishK]

Hi Eric,

I did the fresh install only,

and also ran the add_user_script provided in one of the forum.

Can you please clarify me one thing,

Is the Keystone IP and controller IP will be same as per the IP of my server where I have installed controller.

Or will the Keystone IP will always be default with 127.0.0.1.

Note: I have kept my controller IP (128.88.**.150) in both the scripts ie in add_to_Keystone.sh and also in apps.sh

Please advice me

Regards,

Satish K

[SatishK]

Hi Eric.

Also while creating the user as per ur post above,

When I type the command

$keystone user-create --name sdn

It is respondig as "Service Unavailable (HTTP 503)

Also note that when I ran the connand
$curl --header "X-AUTH-Token:ADMIN" -ksS --request GET --url "http://127.0.0.1:35357/v2.0/tenants" | python -mjson.tool

I am getting the error as "no JSON object could be decoded"

Please advice

Regards,

Satish K

[SatishK]

also if I run the below command.

#curl -Lvfks "$https://128.88.150.151:8443/sdn/v2.0/auth" -d "login":{"domain":"sdn","user":"sdn","password":"skyline"} -H "Content-Type:application/json;"

I  am getting as 403 Forbitten error

[SatishK]

Hi,

Can you please also let me know what is that I need to to consider if I have a proxy server for Creating an user.

Please answer to my all quarries above.. in different posts..

[EricAtHP]

Hi Satish,

Let me see if I can get all of them. :)

127.0.0.1 just means localhost. You can very easily replace it with the real IP address.

Curl commands will use a configured proxy which isn't a good idea with these commands. You can try adding "--noproxy 128.88.150.151" immediately after the curl command:

curl --noproxy 128.88.150.151 --header "X-AUTH-Token:ADMIN" -ksS --request GET --url "http://128.88.150.151:35357/v2.0/tenants" | python -mjson.tool

There are two ways to configure keystone. The first is to use the curl commands documented in the guides, the ones you have been using. The second is to use the keystone cli commands like i documented in an earlier post. The advantage of the keystone cli is that proxy doesn't matter but you do have to run them on the system that is hosting keystone.

It seems like keystone isn't running in your case causing the failures. Both the cli and curl commands work for me.

Here is a controller auth curl command that works for me:

curl -sk -H 'Content-Type:application/json' -d'{"login":{"user":"sdn","password":"skyline","domain":"sdn"}}' https://127.0.0.1:8443/sdn/v2.0/auth | python -mjson.tool

{
    "record": {
        "domainId": "1a0c2a1beb9c4520a773f49f715108f2",
        "domainName": "sdn",
        "expiration": 1413390943000,
        "expirationDate": "2014-10-15 10-35-43 -0600",
        "token": "84624321da044a76a6436e946fb06528",
        "userId": "e9847abd97b04f2f88cbe7feb1c0cf49",
        "userName": "sdn"
    }
}

By the way, the "| python -mjson.tool" command is only used to format the output nicely.

[SatishK]

Hi,

When I tried to create a user on keystone using command,

$keystone user-create --name sdn.

Im getting the below error,

Warning: Bypassing the authendication,

and Service Unavailable (503).

Can you please let me know, also,

What are the proxy settings I need to take care for keysone configuration while adding an user.

regards,

Satish

[EricAtHP]

Hi Satish,

Those keystone cli commands rely on the environment variables at the beginning of the command list I posted. Those environment variables must be reset everytime you login to the controller. You can edit the bash config files too but I don't recommend it.  

For the Icehouse version of keystone:

export OS_SERVICE_TOKEN=ADMIN
export OS_SERVICE_ENDPOINT=http://127.0.0.1:35357/v2.0
keystone user-create --name sdn

[SatishK]

Hi,

Thanks for that response,

What is that I need to take care for proxy related in keystone.conf file.

Regards,

Satish K

[SatishK]

Hi,

Thank you,, for your support.

Now my keystone is working much fine, I did the proxy setting then I can able to add user, role and tenant to it.

But when I run/install the controller the default port is not coming up. ie 8443 is not listing,

when I did netstat I can see the 35357 port is up and listening, but not the 8443.

So I am not able to open the UI page from my firefoz .. https:/127.0.0.1:8443/... ( all the option, like api, auth ,, model etc)

I even tried with proxy setting to noproxy in browers but no gain.

Can you please advice me what is happening or what went wrong.

I can see the sdnc and sdna are up and runnig,

In log i can see one thing..  

Bundle org.eclipse.virgo.medic.core_3.6.2 RELEASE service 38 as service event UNREGISTERING.

When I scrolled a bit above I can see an error saying Ilogservicelistner.

attached is the error log.

Thanks for all,,

Regards,

Satish K

[sdnindia]

Hi Satish,

Please provide the information needed at

http://h30499.www3.hp.com/t5/SDN-Discussions/Cannot-login-to-my-controller/m-p/6651882#M533 .

Thanks,

HP SDN Team

[SatishK]

Hi SDN Team,

I have provided the details. Request you to go throught and Provide your valuable comments.

Regards,

Satish K

[SatishK]

Got resolved,

Further details at

http://h30499.www3.hp.com/t5/SDN-Discussions/Cannot-login-to-my-controller/td-p/6529444/page/2#.VH6khtLoSzs

Regards,

Satish K