[Openstack-devel] [bug] keystone 2013.1-1 MySQL connection string issue

Thomas Goirand thomas at goirand.fr
Wed Apr 10 11:50:49 UTC 2013

On 04/10/2013 07:45 PM, Alberto Molina Coballes wrote:
> Backport Repositories used:
> deb http://33.apt-proxy.gplhost.com/debian grizzly main
> deb http://33.apt-proxy.gplhost.com/debian grizzly-backports main
> keystone: 2013.1-1
> Database: MySQL
> dbconfig-common: yes
> keystone fails to configure using a tcp/ip connection different from
> localhost.
> PKG-Openstack now calling: dbc_go keystone configure
> 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 corot.gonzalonazareno.org
> <mailto:keystone at corot.gonzalonazareno.org>: success.
> verifying access for keystone at corot.gonzalonazareno.org
> <mailto:keystone at corot.gonzalonazareno.org>: success.
> creating database keystonedb: success.
> verifying database keystonedb exists: success.
> dbconfig-common: flushing administrative password
> Traceback (most recent call last):
>   File "/usr/bin/keystone-manage", line 28, in <module>
>     super(Connection, self).__init__(*args, **kwargs2)
> sqlalchemy.exc.OperationalError: (OperationalError) (1045, "Access
> denied for user 'keystone'@'' (using password: YES)") None None
> There is no correspondence between Host Attribute in mysql.user and
> mysql.db tables and the one used during configuration.
> At configuration we chose for MySQL IP address but the
> insert operation was performed with its FQDN, so later connection fails.
> This could be solved using '%' instead like others packages do.
> Alberto


This is likely to be a problem in your MySQL server setup, no? Also, I
fail to see how this is related to Keystone itself, and not to
dbconfig-common (which does the MySQL configuration).

Your thoughts?


More information about the Openstack-devel mailing list