Book Image

Troubleshooting OpenStack

By : Tony Campbell
Book Image

Troubleshooting OpenStack

By: Tony Campbell

Overview of this book

OpenStack is a collection of software projects that work together to provide a cloud fabric. OpenStack is one of the fastest growing open source projects in history that unlocks cloud computing for everyone. With OpenStack, you are able to create public or private clouds on your own hardware. The flexibility and control afforded by OpenStack puts the cloud within reach of anyone willing to learn this technology. Starting with an introduction to OpenStack troubleshooting tools, we’ll walk through each OpenStack service and how you can quickly diagnose, troubleshoot, and correct problems in your OpenStack. Understanding the various projects and how they interact is essential for anyone attempting to troubleshoot an OpenStack cloud. We will start by explaining each of the major components and the dependencies between them, and move on to show you how to identify and utilize an effective set of OpenStack troubleshooting tools and fix common Keystone problems. Next, we will expose you to common errors and problems you may encounter when using the OpenStack Block Storage service (Cinder). We will then examine Heat, the OpenStack Orchestration Service, where you will learn how to trace errors, determine their root cause, and effectively correct the issue. Finally, you will get to know the best practices to architect your OpenStack cloud in order to achieve optimal performance, availability, and reliability.
Table of Contents (17 chapters)
Troubleshooting OpenStack
About the Author
About the Reviewer

Cinder errors

In this section, we will explore a few of the more common errors you might encounter with Cinder. While we highlight just a few of the errors you may come across, the troubleshooting techniques we illustrate should be helpful in various troubleshooting situations.

Missing the cinder-volumes volume group

When using LVM to back Cinder, OpenStack expects there to be a volume group named cinder-volumes. When running the vgdisplay command, you can check for the cinder-volumes volume group as shown here:

If you attempt to create cinder volume without having a volume group named cinder-volumes, it's very likely that your volume will end up in an error state as illustrated in the following screenshot with MyVol2:

You can further confirm that this is the issue by checking the scheduler log at /var/log/cinder/scheduler.log file. In this log file, you are looking for an error similar to the one shown here:

The last line in the log file may point to the fact that No valid host was found, but...