keystone-all should not attempt to run if keystone is in httpd

[Adam Young]

If a user attempts to run keystone-manage but the instance is configured to run in httpd, it will attempt to start the eventlet server. If the httpd instance is running, the error is confusing, since a port is already in use.

[Dolph Mathews (dolph)]

Unable to reproduce in stable/kilo.

[David Stanek (dstanek)]

Should the description here be 'keystone-all should not....'?

[Morgan Fainberg (mdrnstm)]

I'm not sure how keystone-all is meant to know keystone is supposed to run under httpd. I've done a number of test scenarios where I'll configure keystone under both and swap between. The port already in use is a valid error (while cryptic) and correct as it isn't guaranteed to be keystone on the port.

[Morgan Fainberg (mdrnstm)]

What is the thought on keystone being aware of what the deployer has chosen to run?

[Dolph Mathews (dolph)]

That's crazy. Don't try to start the eventlet server if you're already running it in Apache on the same port. More generally, don't try to run any two things on the same port, as the error message already indicates.