On 11/02/2014 05:45 AM, Thomas Goirand wrote: >> root@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@localhost: success. >> verifying access for keystone@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)
The above should be due to bug #767711. Are you using systemd? Could you first create /var/run/keystone, and then try to install keystone, then see if you have the same issue? Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
