[rhos-list] two node configuration with packstack

[Derek Higgins]

On 03/08/2013 09:56 PM, Perry Myers wrote:
> On 03/05/2013 05:41 PM, Aydin PAYKOC wrote:
>> Hi,
>>
>> Perry, many thanks for your answer. I have managed to install
>> openstack with packstack.
>> After the installation when I do "source keystonerc_admin" from the
>> root user and
>> keystone token-get for testing it says "Invalid user / password (HTTP 401)"
>> Also when I do openstack-status it says all the services are active
>> but also says;
>> == Keystone users ==
>> Invalid user / password (HTTP 401)
>> == Glance images ==
>> Invalid user / password (HTTP 401)
>> == Nova instances ==
>> ERROR: Invalid OpenStack Nova credentials
>>
>> I have done a fresh installation and does not changed any passwd.
>>
>> I have than looked to the log files, in all services it there is a
>> line similar to;
>> 1045, "Access denied for user 'nova'@'192.168.100.252' (using
>> password: YES)") None None
>>
>> So I checked mysql login;
>> when I try "mysql -unova -psecret" it logs in without any problem but when I do
>> "mysql -unova -psecret at 192.168.100.252" it gives the message,
this command doesn't look correct to me, try
$ mysql -u nova -psecret -h 192.168.100.252 nova

>> 1045, "Access denied for user 'nova'@'localhost' (using password YES)"
>>
>> Can anyone help me out ?

when running packstack in interactive mode all of the passwords for the
various services are randomly generated. If you run it in interactive
mode a second time then new ones get generated. I think two things are
going on here

1. the various mysql passwords have changed but the services were
running before packstack was run so didn't pick up the changes in the
config files, restarting the services using the wrong password should
solve this

2. the admin password in keystonerc_admin has now changed but because
the keystone user had previously been created with a different password
the new password in keystonerc_admin is now incorrect, if you have the
original admin password you can use this. If you don't have it you can
set a new one using the admin token (admin_token in
/etc/keystone/keystone.conf)
# get the the uuid for the admin user
$ keystone --os-token <admin_token> --os-endpoint
http://127.0.0.1:35357/v2.0/ user-list

# change the password for this user
$ keystone --os-token <admin_token> --os-endpoint
http://127.0.0.1:35357/v2.0/ user-password-update --pass newpassword
<adminuuid>

another option is to start again using an answerfile (after removing
packages, dropping data bases etc...), the benefit of doing this is
running packstack multiple times with the answerfile doesn't have any
undesired side effects.

In general if running packstack multiple times and answer file should be
used so that the randomly generated passwords from the first run don't
change, the newest versions of packstack generates a answerfile when ran
in interactive mode to facilitate this.

hope this helps,
thanks,
Derek.

> 
> Not sure what the problem could be offhand, but one of the other
> engineers on the list should be able to assist you.
> 
> Cheers,
> 
> Perry
> 
> _______________________________________________
> rhos-list mailing list
> rhos-list at redhat.com
> https://www.redhat.com/mailman/listinfo/rhos-list
>