Comment 6 for bug 1046593

This is a case of mis-configuration combined with the lack of a good error message.

The file in which to cache the glance service PID can be configured via the pid-file config option, otherwise it defaults to /var/run/glance/glance-api.pid.

This file path must be writeable by the current user, otherwise glance-control bombs out, *after* spawning the required service but *without* caching the process ID anywhere.

The issue could be addressed by falling back to a temporary pid file in that case, so that at least the user could supply that file to the corresponding glance-contol stop command.