I am using systemd. /var/run/keystone, already exists now. even after purging. does it make sense to install keystone standalone?
here is my config dbc_install='true' dbc_upgrade='true' dbc_remove='' dbc_dbtype='mysql' dbc_dbuser='keystone' dbc_dbpass='2JnTb4mOmQQ3' dbc_dbserver='' dbc_dbport='' dbc_dbname='keystonedb' dbc_dbadmin='root' dbc_basepath='' dbc_ssl='' dbc_authmethod_admin='' dbc_authmethod_user='' sudo aptitude install -t experimental keystone The following NEW packages will be installed: keystone 0 packages upgraded, 1 newly installed, 0 to remove and 2095 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 ... 283839 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) ... debconf: warning: possible database corruption. Will attempt to repair by adding back missing question keystone/passwords-do-not-match. 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@localhost: success. verifying access for keystone@localhost: success. creating database keystonedb: success. verifying database keystonedb exists: success. dbconfig-common: flushing administrative password 2014-11-02 05:01:21.363 9331 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 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! I think i found the problem: root@mdupont-Aspire-7750G:~# /usr/bin/keystone-all Traceback (most recent call last): File "/usr/bin/keystone-all", line 50, in <module> from keystone.openstack.common import processutils ImportError: cannot import name processutils root@mdupont-Aspire-7750G:~# python Python 2.7.8 (default, Oct 18 2014, 12:50:18) [GCC 4.9.1] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import keystone.openstack.common >>> print keystone.openstack.common <module 'keystone.openstack.common' from '/mnt/newdrive2/home/mdupont/experiments/stack/keystone/keystone/openstack/common/__init__.pyc'> It is importing from my previous attemps at installing the devstack! I will remove that. root@mdupont-Aspire-7750G:~# rm -rf /mnt/newdrive2/home/mdupont/experiments/stack/ root@mdupont-Aspire-7750G:~# /usr/bin/keystone-all 2014-11-02 05:09:50.605 10040 WARNING keystone.openstack.common.versionutils [-] Deprecated: keystone.middleware.core.XmlBodyMiddleware is deprecated as of Icehouse in favor of support for "application/json" only and may be removed in Kilo. 2014-11-02 05:09:50.644 10040 WARNING keystone.openstack.common.versionutils [-] Deprecated: keystone.contrib.revoke.backends.kvs is deprecated as of Juno in favor of keystone.contrib.revoke.backends.sql and may be removed in Kilo. And now it works! omg it was the devstack leftovers, how can root be trying to find python there? well that is where it told devstack to install it. I am sorry about the mess and confusion here. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org