To figure out exactly what could be wrong in an OpenStack cluster, you should go through a certain number of steps. With several moving services that run OpenStack, troubleshooting a specific component should be addressed independently. For example, the Sahara service might generate a generic error while launching a cluster. The best and fastest way to work around such a problem is to address directly the root cause.
OpenStack provides an amazing command-line utility allowing the checking of the status of services that should run on every OpenStack node as specified during the packstack installation. For example, to check the status of the OpenStack services running on the cloud controller node, run the openstack-status command line as follows:
# openstack-status
The previous command-line output illustrates the following:
openstack-nova-compute: Inactive since the nova service is running in a different compute node.openstack-keystone: Is active...