Local keystone credential script fails with 2.4.3.0595

[fwindt]

Hi, 

I'm trying to evaluate the HP SDN controller (version 2.4.3.0595). Installation of the controller as well as keystone (icehouse) works fine, but the script that is supposed to populate the keystone store with the sdn/skyline credentials errors out. I tried looking around the forums but couldn't find any matching install instructions, it appears past controller versions used different ways to do this. Below some more detailed information. Does anyone know how to fix this, or what the current manual credential creation steps are? 

# lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 12.04.5 LTS
Release:	12.04
Codename:	precise

# grep -ir icehouse /etc/apt/
/etc/apt/sources.list.d/cloudarchive-icehouse.list:deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/icehouse main
/etc/apt/sources.list.d/cloudarchive-icehouse.list:deb-src http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/icehouse main

# apt-get install keystone
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  keystone
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 0 B/14.8 kB of archives.
After this operation, 128 kB of additional disk space will be used.
Preconfiguring packages ...
Selecting previously unselected package keystone.
(Reading database ... 60778 files and directories currently installed.)
Unpacking keystone (from .../keystone_2012.1.3+stable-20130423-f48dd0fc-0ubuntu1.1_all.deb) ...
Processing triggers for man-db ...
Processing triggers for ureadahead ...
Setting up keystone (2012.1.3+stable-20130423-f48dd0fc-0ubuntu1.1) ...
keystone start/running, process 2999

# curl --noproxy  -i http://localhost:35357/v2.0/users -H "X-Auth-Token: ADMIN"
{"users": []}

# /opt/sdn/admin/config_local_keystone
Adding SDN-related items to Keystone...
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/tmp/keystone_config.py", line 67, in config_roles
    tid=get_id(proto, host_port, header, tenants_url, "tenants", "sdn")
  File "/tmp/keystone_config.py", line 23, in get_id
    root_node = json.loads(resp).get(root)
  File "/usr/lib/python2.7/json/__init__.py", line 326, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python2.7/json/decoder.py", line 369, in decode
    raise ValueError(errmsg("Extra data", s, end, len(s)))
ValueError: Extra data&colon; line 1 column 4 - line 5 column 4 (char 4 - 52)
Error: Creating tenant, users, roles and association failed
Create response:
#

On a different note, is it possible to use this product as is (currently using free trial, but more than willing to buy a license) to manually insert 10-30 flows into an HP5900AF, much like you can do with ODL?

thanks,

felix

[Gerhard Roets]

Hi Felix

I am busy looking into this and will keep you posted.

Kind Regards

Gerhard Roets

HP SDN Team

[Gerhard Roets · Accepted solution]

Hi Felix

I suspect you did not do an apt-get update after adding the icehouse repository. I have contacted our documentation team to look into this urgently.

Following the current instructions to the letter I get the following
After Step 2.1
gpr@sdnctrl24-18:~$ dpkg -l keystone
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version        Description
+++-==============-==============-============================================
ii  keystone       2012.1.3+stabl OpenStack identity service - Daemons

This number alligns with the number in your output

Selecting previously unselected package keystone.
(Reading database ... 60778 files and directories currently installed.)
Unpacking keystone (from .../keystone_2012.1.3+stable-20130423-f48dd0fc-0ubuntu1.1_all.deb) ...

... Installed controller etc

With Step 2.4
I get the same error as you

Now to repair your setup
As root do the following
dpkg -P keystone
rm /var/lib/keystone/keystone.db   (Or back it up it should nto contain anything usefull for you at this point)
apt-get update (Be sure that this apt update goes through, you need to do this update after you added the repo for icehouse)
apt-get install keystone (You will notice a bunch of new items being installed)
apt-get upgrade (You will need to do this since some of the python libraries will need to be updated for keystone so all is in sync with the update)

root@chewbecca-18:~# dpkg -l keystone
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version        Description
+++-==============-==============-============================================
ii  keystone       1:2014.1.3-0ub OpenStack identity service - Daemons

The above version is the real icehouse version ;)

Then after the above
root@sdnctrl24-18:~# /opt/sdn/admin/config_local_keystone
Adding SDN-related items to Keystone...
keystone stop/waiting
keystone start/running, process 8539
Finalize configuration for keystone...
...done.

I confirmed I can login to the gui now.

Just for reference this is what the steps should look like
The steps that should work from a clean install
1. Point the Ubuntu system to the most recent package meta-data:
~$ sudo apt-get update
2. Use the following commands to install the Keystone server on the local machine.
~$ sudo apt-get install python-software-properties
ubuntu-cloud-keyring
~$ sudo add-apt-repository cloud-archive:icehouse
          NOTE: Hewlett-Packard recommends using the “icehouse” version of the
          OpenStack Keystone server, as shown in the above command. However, you can
          use any of the following Keystone server options:
                    -icehouse (recommended)
                    -havana
                    -grizzly
                   -folsom

~$ sudo apt-get update

~$ sudo apt-get install keystone

Kind Regards

Gerhard Roets

[fwindt]

I indeed had not run an 'apt-get update' after adding the repo, and to be honest I should have thought of trying that.

Your fix worked a treat, I'm in now. Thank you kindly for your help, I appreciate it!

felix