No errors when creating keystone tables when MySQL fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Expired
|
Undecided
|
Unassigned | ||
openstack-manuals |
Invalid
|
Undecided
|
Unassigned |
Bug Description
By following documentation:
http://
When MySQL controller is not changed in /etc/keystone/
Then when you are using "su -s /bin/sh -c "keystone-manage db_sync" keystone" command won't produce any errors.. errors appear only when you add an user for example:
keystone user-create --name=admin --pass=password --<email address hidden>
An unexpected error prevented the server from fulfilling your request. (HTTP 500)
In keystone.log file there will be:
CRITICAL keystone [-] OperationalError: (OperationalError) (2005, "Unknown MySQL server host 'controller' (1)") None None
If controller is changed in /etc/keystone/
su -s /bin/sh -c "keystone-manage db_sync" keystone
otherwise when they try to create an user they will receive the error above and error in keystone.log
TRACE keystone.
tags: | added: user-experience |
Changed in keystone: | |
status: | Incomplete → New |
Changed in keystone: | |
status: | New → Incomplete |
There must be something else at play here, because you should be seeing the stderr you're expecting.
Running keystone-manage directly or with su -s (exactly as described in openstack-manuals) both produce a relevant error message for me. For example:
$ keystone-manage db_sync 2> stderr.log
$ cat stderr.log
2014-04-29 10:31:17.072 35866 CRITICAL keystone [-] OperationalError: (OperationalError) (2005, "Unknown MySQL server host 'controller' (0)") None None