keystone auth silently fails if Rabbit is unavailable

[Jodie Miu]

If for any reason the service named rabbitmq-server.service is unavailable, keystone authentication fails. Looking at the output of openstack token issue --debug, you get this:
Making authentication request to http://192.0.2.1:5000/v2.0/tokens
Resetting dropped connection: 192.0.2.1

It just stays there for an eternity (unconfirmed) or until the user gets frustrated and kills it. The fact that keystone auth fails that way means that all OpenStack services similarly lag (Nova, Heat, etc). Curiously enough, rabbitmq-server was reported as being active and running, but I tried restarting it anyway. Keystone auth works now. Can reproduce this simply by stopping rabbitmq-server and trying to do things that require Keystone auth.

[Steve Martinelli (stevemar)]

This feels somewhat out of scope for Keystone. Aside from better error reporting I'm not sure what there is to do here. If your rabbit mq is down or unavailable there will be many other apps that fail.

[Lance Bragstad (lbragstad)]

Automatically unassigning due to inactivity.

[Steve Martinelli (stevemar)]

See previous comment