Hi Anthony,
Yes, the credentials in keystone.conf do work. As I say, the problem
is that Keystone doesn't seem to be using those credentials now I've
converted it to use Apache/mod_wsgi. The username it's using is
different, and it may be the password it's using is different. What's
not clear to me is where it's picking up those non-working
credentials.
Cheers,
Adam
On Mon, Jun 30, 2014 at 12:05 AM, Anthony Vattathil
<avattathil(a)gmail.com> wrote:
Adam,
Look at the keystone.conf search for connection parameter.
Verify that you can login directly into mysql using those credentials and
that you can access the database with that user.
Also another thing make sure that the upgrade didn't put a default entry
above the connection string.
Hope that helps
--Tony
tonyv(a)redhat.com
On Sunday, June 29, 2014, Adam Huffman <adam.huffman(a)gmail.com> wrote:
>
> I'm in the middle of changing my Icehouse Keystone to use Apache with
> SSL. After implementing this change, I'm seeing a strange MySQL error
> when I submit a keystone query e.g. 'endpoint-list':
>
> 2014-06-29 22:38:41.172 30284 TRACE keystone.common.wsgi
> OperationalError: (OperationalError) (1045, "Access denied for user
> 'keystone'@'localhost' (using password: YES)") None None
>
> The weird thing is that the user defined in
> /etc/keystone/keystone.conf is in fact 'keystone_admin', as created
> when this cloud was setup originally using RDO. From where is it
> picking up that username?
>
> I created a new MySQL user 'keystone' with the same privileges as
> 'keystone_admin' but that didn't make any difference.
>
> Adam
>
> _______________________________________________
> Rdo-list mailing list
> Rdo-list(a)redhat.com
>
https://www.redhat.com/mailman/listinfo/rdo-list