Chapter 9. Troubleshooting

This chapter contains some advice to help analyze and resolve problems that might occur during the deployment of your Red Hat Enterprise Linux OpenStack Platform environment.

9.1. Defining the Provisioning Process

The Red Hat Enterprise Linux OpenStack Platform installer has two main steps when provisioning each host:
  • Building - The building process occurs through PXE network boot. The installer applies a kickstart configuration to build the initial host operating system. This process involves:
    • Installing the operating system, which you defined during the rhel-osp-installer stage.
    • Configuring network interfaces.
    • Registering the system and attaching Red Hat product subscriptions.
    • Installing Puppet for the configuration process.
  • Configuration - The configuration process occurs when the host's building process successfully completes. This configuration process uses a set of Puppet modules to install and configure the required OpenStack services for your environment. The installer communicates with a Puppet Agent installed on each host to apply the configuration from each module.
The provisioning and configuration process further breaks into specific tasks that the installer completes. You can view these tasks in the Dynflow console for the deployment task. To access the Task page for your deployment, click Show more details under the progress bar on the Deployment page. From there, click the Dynflow Console.
These Dynflow Console displays a combination of subtasks associated with your deployment. Knowing the functions of each subtask helps with determining the deployment stage. These subtasks are:
Updates a host's attributes.
Starts the provisioning process for a new host. This includes resetting the host and PXE booting to the provisioning templates assigned to the host.
Waits until the host provisioning process completes. This item completes when the host finishes running through the kickstart provisioning template.
Checks if a particular host is ready to accept SSH connections. This is so the installer can start the Puppet Agent on the host.
Starts configuration on the host using Puppet Agent.
Waits until the Puppet Agent on the host completes configuration and sends a report.
Checks if the host has any outstanding errors from the last Puppet Agent report.