This page contains a sortable table of common problems and solutions, as well as tips on how to troubleshoot your OpenStack deployment both during and after installation.
For a complete list of bugs, see: https://bugs.launchpad.net/openstack-cisco
Common Issues and Solutions
The following table contains commonly asked questions, known issues, and bugs. Puppet Warning and Error messages are included. Solutions and workarounds are provided where possible.
|i.0 and earlier||All in One||Swift|| Puppet error: Swift swift-container-replicator, swift-container-sync, or swift-account-replicator will not start. For example, Puppet logs the following message: || Start Swift manually: |
|Any||Full HA||Ceph||Ceph-backed cloud is not working properly.||Perform a second Puppet catalog run.|
|Any||Any||Neutron||Neutron server does not start when using the Cisco plugin.|| Start |
|Any||Any||Neutron||Neutron's Firewall as a Service does not start.|| When starting the Neutron level 3 agent, include the following argument: |
|h.2 and later||Any||Nova||Live migration does not work with NFS storage.||Ensure that the Nova user ID and GID is the same on all systems.|
|Any||Any||Cobbler||My OpenStack nodes do not have a default gateway.|| To enable default routes, remove the |
|Any||2 Role||Puppet|| The Puppet run is very short and contains the message: || Check for the build node line in the |
|h.1 and earlier||All in One||Puppet|| Warning message: ||This message should disappear if you do another Puppet catalog run. See Bug #1282281.|
|Any||Any||Swift|| Warning message: ||This message is harmless; ignore it. See Bug #1289187.|
|h.3 and earlier||Any||Keystone|| Warning message: ||This message is harmless; ignore it.|
|h.3 and earlier||Any||Nagios||Warning about nagios services restarting.||This message is harmless; ignore it. The message is thrown by the example configuration of nagios that is installed by default.|
|h.3 and earlier||Full HA||MongoDB||Warning about mongodb in HA scenarios.||This message is harmless; ignore it. In HA scenarios, Mongodb will throw warnings until all three nodes are up, a quorum is formed, and a primary node elected, at which point the warnings will stop.|
|Any||Any||Cobbler|| Warning message: ||This message is harmless; ignore it. See Bug #1238118.|
|i.0||Multi-node||Neutron||VMs in a GRE network do not receive IP addresses via DHCP.|| Fixed in i.1.
See Bug #1327294
|h.2 and earlier||All in One||Graphite|| ||Perform a second Puppet catalog run. See Bug #1282239|
|i.0||High Availability||Keystone|| || Synch the Keystone database manually:
|i.0||Any||Nova|| || Create the database manually:
|i.0||High Availability||Cobbler|| Error messages of the form: || Copy the file |
Reading Puppet Logfiles
Puppet generates a large volume of messages during a catalog run, but most of the time only error and warning messages are of concern. Errors will stop the Puppet run; warnings will not. Many of the warnings seen during puppet runs are harmless. See Common Issues and Solutions for common Puppet warning messages and their meanings.
Using OpenStack Logs for Troubleshooting
The logfiles for OpenStack services are one of the primary tools for troubleshooting problems with OpenStack.
Most OpenStack logfiles are named following this convention:
For example, logs from the glance-api service are found in:
Logs from the nova-api service are found in:
If you don't see a log for the service you're trying to troubleshoot, look in:
A log file is sometimes created there instead.
It may help in troubleshooting to enable verbose (more detailed diagnostic messages) logging or debug (lower level traces) logging for an OpenStack service or for all OpenStack services.
To enable verbose or debug logging for an OpenStack service:
- Edit the service's configuration file.
- In the file, set the verbose or debug boolean to True.
- Save the file.
- Restart the service.
Note: Some OpenStack services might not have verbose or debug flags. Instead, you can try enabling verbose or debug logging for all OpenStack services, below.
To enable verbose or debug logging for all OpenStack services:
- In the file, set the verbose or debug flag to true:
- Save the file.
- Do a Puppet catalog run or restart Puppet.