openstack service create command throwing "Internal Server Error (HTTP 500)"

asked 2018-07-24 01:03:02 -0500

vamsee_007 gravatar image

updated 2018-07-26 08:14:08 -0500

I'm trying setup Openstack multi node environment in my CentOS VM. I've successfully installed the openstack Queens v. in both controllernode and compute node. When i try to create a service in controllernode, its throwing the following error: Internal Server Error (HTTP 500)

The command is: openstack service create --name keystone --description "OpenStack Identity" identity

The keystone.log file is as follows:

2018-07-24 11:10:19.210 5770 WARNING oslo_log.versionutils [-] Deprecated: UUID Token Provider "[token] provider=uuid" is deprecated as of Pike in favor of Fernet token Provider "[token] provider=fernet" and may be removed in R. 
2018-07-24 11:10:19.212 5770 WARNING oslo_config.cfg [-] Option "driver" from group "token" is deprecated for removal.  Its value may be silently ignored in the future. 
2018-07-24 11:10:19.213 5770 WARNING stevedore.named [-] Could not load memcache

The Keystone Bootstrap command is as follows:

keystone-manage bootstrap --bootstrap-password openstack --bootstrap-admin-url http://controllernode1:5000/v3/ --bootstrap-internal-url http://controllernode1:5000/v3/ --bootstrap-public-url http://controllernode1:5000/v3/ --bootstrap-region-id RegionOne

The environment variables are as follows:


Error in the Keystone-error.log:

2018-07-26 14:42:21.279222 ImportError: (u'Unable to find %(name)r driver in %(namespace)r.', {'namespace': 'keystone.token.persistence', 'name': 'memcache'})
2018-07-26 14:42:25.097350 mod_wsgi (pid=7468): Target WSGI script '/usr/bin/keystone-wsgi-public' cannot be loaded as Python module.
2018-07-26 14:42:25.097435 mod_wsgi (pid=7468): Exception occurred processing WSGI script '/usr/bin/keystone-wsgi-public'.
2018-07-26 14:42:25.097503 Traceback (most recent call last):
2018-07-26 14:42:25.097549   File "/usr/bin/keystone-wsgi-public", line 54, in <module>
2018-07-26 14:42:25.097773     application = initialize_public_application()
2018-07-26 14:42:25.097812   File "/usr/lib/python2.7/site-packages/keystone/server/", line 134, in initialize_public_application
2018-07-26 14:42:25.098076     config_files=_get_config_files())
2018-07-26 14:42:25.098123   File "/usr/lib/python2.7/site-packages/keystone/server/", line 66, in initialize_application
2018-07-26 14:42:25.098185     startup_application_fn=loadapp)
2018-07-26 14:42:25.098216   File "/usr/lib/python2.7/site-packages/keystone/server/", line 46, in setup_backends
2018-07-26 14:42:25.098381     drivers = backends.load_backends()
2018-07-26 14:42:25.098418   File "/usr/lib/python2.7/site-packages/keystone/server/", line 55, in load_backends
2018-07-26 14:42:25.098589     drivers = {d._provides_api: d() for d in managers}
2018-07-26 14:42:25.098653   File "/usr/lib/python2.7/site-packages/keystone/server/", line 55, in <dictcomp>
2018-07-26 14:42:25.098713     drivers = {d._provides_api: d() for d in managers}
2018-07-26 14:42:25.098743   File "/usr/lib/python2.7/site-packages/keystone/token/persistence/", line 48, in __init__
2018-07-26 14:42:25.099084     super(PersistenceManager, self).__init__(CONF.token.driver)
2018-07-26 14:42:25.099129   File "/usr/lib/python2.7/site-packages/keystone/common/", line 181, in __init__
2018-07-26 14:42:25.099357     self.driver = load_driver(self.driver_namespace, driver_name)
2018-07-26 14:42:25.099392   File "/usr/lib/python2.7/site-packages ...
edit retag flag offensive close merge delete


Check the keystone log for ERROR logs. You probably find it under /var/log/keystone.

Such errors are typically caused by some misconfiguration, such as a typo in the keystone.conf file.

Bernd Bausch gravatar imageBernd Bausch ( 2018-07-24 01:12:34 -0500 )edit

Thanks for the prompt reply. I've updated the question with the log data, can you please help?

vamsee_007 gravatar imagevamsee_007 ( 2018-07-24 01:18:23 -0500 )edit

Did you install and configure memcached as described here?

eblock gravatar imageeblock ( 2018-07-24 02:03:46 -0500 )edit

By the way, you mention installing Queens version. But your command is from older releases. Since Newton release (I'm not sure) the keystone service is deployed with a bootstrap command:

keystone-manage bootstrap --bootstrap-password ADMIN_PASS [...]
eblock gravatar imageeblock ( 2018-07-24 02:09:41 -0500 )edit

Hi @eblock , I've tried with the keystone bootstrap command. can you please guide me the next step?

vamsee_007 gravatar imagevamsee_007 ( 2018-07-24 02:28:42 -0500 )edit

Well, you have to follow the guide, it explains every step in detail better than I could. Make sure you use a consistent workflow such as staying within one install guide and following it from A to Z. Don't leave out steps unless you are sure you already completed them and such.

eblock gravatar imageeblock ( 2018-07-24 02:42:45 -0500 )edit

You "tried the keystone bootstrap" command, what was the result? Did it work? Analyze the results and logs and try to resolve the problems. If something doesn't work as expected, it's probable that you missed a step or had a typo or something. In that case double check the steps from the guide.

eblock gravatar imageeblock ( 2018-07-24 02:45:52 -0500 )edit

Thanks! Can't see any progress. I'm following a video in youtube. After the bootstrap command, how to create the keystone service? Please just guide me through any doc.

vamsee_007 gravatar imagevamsee_007 ( 2018-07-24 08:49:18 -0500 )edit

Keystone installation is documented at The bootstrap command mentioned by eblock is step 5 at It creates the service.

Bernd Bausch gravatar imageBernd Bausch ( 2018-07-24 09:52:32 -0500 )edit

Thanks Guys!

vamsee_007 gravatar imagevamsee_007 ( 2018-07-25 01:23:38 -0500 )edit

@Bernd Baush this time i've followed the doc in the link but when i try to create a domain its throwing the following error: Failed to discover available identity versions when contacting http://controllernode1:5000/v3. Attempting to parse version from URL. Internal Server Error (HTTP 500)

vamsee_007 gravatar imagevamsee_007 ( 2018-07-25 05:20:26 -0500 )edit

Please paste the used command to execute the keystone-bootstrap script? Of course, any sensitive information should be replaced. And please also paste which environment variables you exported:

env | grep OS_

it's likely that those parameters don't match so your authentication fails.

eblock gravatar imageeblock ( 2018-07-25 08:06:57 -0500 )edit

You can also try to access http://controllernode1:5000/v3 manually. Most likely, this will fail. My guess is that Keystone doesn’t run at all, or as eblock suggests, it listens on a different address/port.

Bernd Bausch gravatar imageBernd Bausch ( 2018-07-25 15:57:21 -0500 )edit

@eblock I've edited the question, Please check once and can you lemme know what the mistake is. Thanks in advance

vamsee_007 gravatar imagevamsee_007 ( 2018-07-26 01:10:35 -0500 )edit

Is apache up and running? Do you see anything in the keystone and apache logs?

eblock gravatar imageeblock ( 2018-07-26 03:56:06 -0500 )edit

You need to understand how Keystone is deployed. It’s the web server that is supposed to listen at port 5000. If all goes well, it passes the request on to Keystone via the WSGI protocol. If anything in the chain between the network port and Keystone is broken, you will be unable to access this URL.

Bernd Bausch gravatar imageBernd Bausch ( 2018-07-26 04:44:58 -0500 )edit

Port 5000 may be blocked by a firewall. The webserver may be dead or not configured correctly. Keystone may be dead. To find out what it is, check if all systemd services are active, check the network ports and firewall, look into the web server and keystone log files.

Bernd Bausch gravatar imageBernd Bausch ( 2018-07-26 04:47:32 -0500 )edit

@eblock The apache service is running. I've update the question with the errors in Keystone-Error.log. Please check

vamsee_007 gravatar imagevamsee_007 ( 2018-07-26 04:58:10 -0500 )edit

The errors still mention memcache, did you install and start it as I already commented? Once again, you really need to go through all the required steps in the guide to bring openstack up.

eblock gravatar imageeblock ( 2018-07-26 05:07:26 -0500 )edit

@eblock Yes I've followed the steps you suggested.

vamsee_007 gravatar imagevamsee_007 ( 2018-07-26 05:20:26 -0500 )edit

@BerndBaush Everything is fine except firewalld. When i try to stop the firewalld service its failing. Is there any way to sort out this issue?

vamsee_007 gravatar imagevamsee_007 ( 2018-07-26 05:34:13 -0500 )edit