OpenStack installation database configure makes HTTP 500 ERROR

Bug #1570699 reported by jianqingjiang
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack (Ubuntu)
New
Undecided
Unassigned

Bug Description

-----------------------------------
Release: 0.1 on 2016-04-13 06:51
SHA: 97286840e4879e0e0ec745b9c813d396f218f032
Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide/source/keystone-install.rst
URL: http://docs.openstack.org/liberty/install-guide-rdo/keystone-install.html

My Controller's hostname is controller
So When I configure every service component, For example keystone, I follow the offical OpenStack installation guide
http://docs.openstack.org/liberty/install-guide-rdo/keystone-install.html#install-and-configure-components
I add

[database]
...
connection = mysql://keystone:KEYSTONE_DBPASS@controller/keystone

But get error below,
"
ERROR (InternalServerError): An unexpected error prevented the server from fulfilling your request. (HTTP 500) (Request-ID: req-dd240e79-2b79-4e55-8ba5-3a156c3266be)
An unexpected error prevented the server from fulfilling your request. (HTTP 500) (Request-ID: req-4428638b-7a4c-471e-8ffe-da4f5184db15)
"

When I change "controller" to "localhost" , it works out .

[database]
...
connection = mysql://keystone:KEYSTONE_DBPASS@localhost/keystone

And every service component configuration should do this way.

Tags: bug text-based
information type: Public → Public Security
Revision history for this message
star (976915210-r) wrote :

Good , same bug affected me

Revision history for this message
Tom Fifield (fifieldt) wrote :

Hi,

Thanks for the report.

Did you follow the instructions to configure name resolution?

http://docs.openstack.org/liberty/install-guide-rdo/environment-networking-controller.html

information type: Public Security → Public
Revision history for this message
jianqingjiang (18367826256-3) wrote :

@fifieldt Yes,I did.

Revision history for this message
Tom Fifield (fifieldt) wrote :

OK, can you please enable debug logging and produce the full log so we can look at why that is happening?

Unfortunately, the localhost fix isn't appropriate for this guide, since the database can live on a different server.

Changed in openstack-manuals:
status: New → Incomplete
Revision history for this message
jianqingjiang (18367826256-3) wrote :
Download full text (5.0 KiB)

This is the log in /var/log/keystone/keystone.log

2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi return self._connection_cls(self, **kwargs)
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 72, in __init__
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi if connection is not None else engine.raw_connection()
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 2104, in raw_connection
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi self.pool.unique_connection, _connection)
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 2078, in _wrap_pool_connect
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi e, dialect, self)
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1401, in _handle_dbapi_exception_noconnection
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi util.raise_from_cause(newraise, exc_info)
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi File "/usr/lib64/python2.7/site-packages/sqlalchemy/util/compat.py", line 200, in raise_from_cause
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi reraise(type(exception), exception, tb=exc_tb)
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 2074, in _wrap_pool_connect
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi return fn()
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi File "/usr/lib64/python2.7/site-packages/sqlalchemy/pool.py", line 318, in unique_connection
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi return _ConnectionFairy._checkout(self)
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi File "/usr/lib64/python2.7/site-packages/sqlalchemy/pool.py", line 713, in _checkout
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi fairy = _ConnectionRecord.checkout(pool)
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi File "/usr/lib64/python2.7/site-packages/sqlalchemy/pool.py", line 480, in checkout
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi rec = pool._do_get()
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi File "/usr/lib64/python2.7/site-packages/sqlalchemy/pool.py", line 1060, in _do_get
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi self._dec_overflow()
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi File "/usr/lib64/python2.7/site-packages/sqlalchemy/util/langhelpers.py", line 60, in __exit__
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi compat.reraise(exc_type, exc_value, exc_tb)
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi File "/usr/lib64/python2.7/site-packages/sqlalchemy/pool.py", line 1057, in _do_get
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi return self._create_connection()
2016-04-15 02:27:03.149 7302 ERROR keystone.common.wsgi File "/usr/lib64/p...

Read more...

Revision history for this message
Sharat Sharma (sharat-sharma) wrote :

Try giving ip address instead of controller. That probably works most of the time. Check if controller is properly mapped to the controller ip address in /etc/hosts

Revision history for this message
jianqingjiang (18367826256-3) wrote :

@Sharat Sharma Thanks, I wrote controller in /etc/hosts and I ping controller is OK

Changed in openstack-manuals:
status: Incomplete → Invalid
no longer affects: openstack-manuals
Paul White (paulw2u)
affects: ubuntu → openstack (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.