[PKG-Openstack-devel] Bug#767574: Bug#767574: Bug#767574: keystone: Does not install : dpkg: error processing package keystone (--configure):

[Thomas Goirand]

Hi Mike,

You're sending your mails to:
- me
- the bug tracker
- the list

Messages to the bug tracker (eg: to 767574 at bugs.debian.org) are
forwarded to the list. Then I am subscribed to the list. So, all
together, I'm receiving all of your messages 3 times. Could you please
just reply to the bug tracker and that's it? Thanks!

Also, as a general rule in Debian, please don't top-post.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

On 11/01/2014 09:03 PM, Mike Dupont wrote:
> I purged and deleted the installation, also removed all open stack
> stuff (as before there was no other open stack modules running)
> It does not tell me what modules it require to run, so obviously it
> cannot run. that might be a minor bug in the dependancies. otherwise I
> get a proper error message.

I'm not sure if I understand the above. :(

> these open stack modules are so
> interdependant. Where do I get the token and what modules are needed
> to test keystone on its own?

To test if keystone works well, you would do, for example (after
installing python-keystoneclient and setting your credentials in your
environment):
keystone service-list

> root at mdupont-Aspire-7750G:~# aptitude install -t experimental keystone
> python-keystone
> The following NEW packages will be installed:
>   keystone
> 0 packages upgraded, 1 newly installed, 0 to remove and 2096 not upgraded.
> Need to get 0 B/69.5 kB of archives. After unpacking 314 kB will be used.
> debconf: delaying package configuration, since apt-utils is not installed
> Selecting previously unselected package keystone.
> (Reading database ... 283730 files and directories currently installed.)
> Preparing to unpack .../keystone_2014.2-1_all.deb ...
> Unpacking keystone (2014.2-1) ...
> Processing triggers for man-db (2.6.7.1-1) ...
> Setting up keystone (2014.2-1) ...
> PKG-Openstack now calling: dbc_go keystone configure
> usermod: no changes
> dbconfig-common: writing config to /etc/dbconfig-common/keystone.conf
> 
> Creating config file /etc/dbconfig-common/keystone.conf with new version
> granting access to database keystonedb for keystone at localhost: success.
> verifying access for keystone at localhost: success.
> creating database keystonedb: success.
> verifying database keystonedb exists: success.
> dbconfig-common: flushing administrative password
> 2014-11-01 08:01:02.895 4680 WARNING keystone.cli [-] keystone-manage
> pki_setup is not recommended for production use.
> Sleeping 5 seconds to make sure the keystone daemon is up and running:
> 5...4...3...2...1...0

The above looks weird to me, because it looks like your keystone daemon
is never started. As as a consequence, you get the error messages below.

> Upgrading db... Creating tenants... Unable to establish connection to
> http://127.0.0.1:35357/v2.0/users
> Unable to establish connection to http://127.0.0.1:35357/v2.0/tenants
> Unable to establish connection to http://127.0.0.1:35357/v2.0/OS-KSADM/roles
> Unable to establish connection to http://127.0.0.1:35357/v2.0/OS-KSADM/roles
> Unable to establish connection to http://127.0.0.1:35357/v2.0/OS-KSADM/roles
> usage: keystone user-role-add --user <user> --role <role> [--tenant <tenant>]
> keystone user-role-add: error: argument --user/--user-id/--user_id:
> expected one argument
> usage: keystone user-role-add --user <user> --role <role> [--tenant <tenant>]
> keystone user-role-add: error: argument --user/--user-id/--user_id:
> expected one argument
> usage: keystone user-role-add --user <user> --role <role> [--tenant <tenant>]
> keystone user-role-add: error: argument --user/--user-id/--user_id:
> expected one argument
> usage: keystone tenant-update [--name <tenant_name>]
>                               [--description <tenant-description>]
>                               [--enabled <true|false>]
>                               <tenant>
> keystone tenant-update: error: too few arguments
> Registering keystone endpoint...Unable to establish connection to
> http://192.168.2.2:35357/v2.0/OS-KSADM/services
> Unable to establish connection to
> http://192.168.2.2:35357/v2.0/OS-KSADM/services/
> done!

Though I just tried to install keystone, and I didn't have that. It all
worked fine for me... So you may have done something wrong somewhere.
Could you try to manually start keystone form the command line and see
what's going on?

Cheers,

Thomas Goirand (zigo)