Keystone not available after Cinder install
When I install Cinder (Stein release) all goes well until I get to the verify step:
openstack volume service list
That command reports that "The Keystone service is temporarily unavailable." and that I should try again later. I have verified everything I can think of (spelling, capitalization, etc.) in the config files and installation commands. I've also run the same command with the --debug option and captured the output, and I've looked at that until my eyes defocus. I've reviewed several other "Keystone service unavailable" posts, but none of them seem to have any bearing on my symptoms.
Any suggestions would be appreciated. If someone would like to see the captured output, I'd be glad to post it, but it's 23KB and the attachment feature on this forum won't accept anything but image files.
You can share text files on paste.openstack.org.
I would check the authentication section in cinder.conf and compare it with equivalent sections in the Nova, Neutron and Glance configuration. Also check if Keystone is up at all by issuing Keystone commands.
I ran
$ sudo grep auth_url sudo find /etc -name "*.conf"
and all the auth_url entries are identical: http://controller:5000/v3. This matches OS_AUTH_URL in my environment. I can't find a list of Keystone commands, but the following all work correctly: (To be continued...)$ openstack user list $ openstack service list $ openstack role list
This works (empty list returned): $ openstack volume list
But this fails: $ openstack volume service list
I pasted the output of
$ openstack --debug volume service list
here: http://paste.openstack.org/show/786438/I would check the Cinder API log for message pertaining to Keystone. Probably "Keystone unavailable; marking token as invalid and deferring auth decision". My hope is that messages shortly prior to this contain details as to why Cinder is unable to connect to Keystone.
The test whose results you pasted has a request ID of req-8be146b2-eed1-4e36-bff5-03162baa0596. Again, looking for Cinder API log messages that contain this request ID should help.