Installing and Configuring OpenStack (Juno) in Oracle® Solaris

Exit Print View

Updated: June 2016
 
 

Investigating and Resolving Problems

This section describes some problems that you might encounter when you install and configure OpenStack.

The following example shows error pertaining to the dashboard.

Error: Unauthorized: Unable to retrieve usage information.
Error: Unauthorized: Unable to retrieve quota information.
Error: Unauthorized: Unable to retrieve project list information.
Error: Unauthorized: Unable to retrieve instance list information.

These messages might indicate that the RSA host key has been changed and has not been propagated to all the components. For more information on configuring RSA keys, refer to How to Install and Configure Neutron and How to Configure the Compute Node.

The following error report might be included in the nova-scheduler log.

controller# grep error `svcs -L nova-scheduler`
2014-12-03 12:49:19.271 3475 TRACE
nova.openstack.common.rpc.common error: [Errno 32] Broken pipe

A broken pipe error is typically reported when you refresh one OpenStack service and not the others. If you made any changes in the configuration files on a node, refresh all the services on the node. The following command restarts services that are online services but need to be refreshed.

controller# svcs \*openstack\* | grep online  \
| awk -e '{print $3}' | xargs svcadm restart

An error can also be due to lack of resources. During the creation of a VM instance, the nova-compute log might display messages similar to the following:

[abc-123-def-456] Build of instance
abc-123-def-456 aborted: Image
xyz-987-uvw-654 is unacceptable: Image query failed.
Possibly invalid or corrupt. Log file location: controller:/tmp/archive_log.4249

Further, the log would also indicate out of space/storage. Use the top command to view the resources on the system. If the system has less than 1GB of memory, you might need to add more.