The new host is now assigned to the Compute deployment role and its networking is configured. The final step is to deploy the new host.
Pro ced u re 8.4 . Dep lo yin g New Ho st s f o r Red Hat En t erp rise Lin u x O p en St ack Plat f o rm 1. Click D epl o y to open the deployment confirmation screen.
Fig u re 8.4 . T h e d ep lo ymen t co n f irmat io n screen
Note
Clicking D epl o y registers the nodes and consumes entitlements. If you perform multiple deployments, you may need to first remove the existing environment from Subscri pti o n Manag er, if applicable.
2. Click D epl o y.
The new host moves to the pro d ucti o n environment, which contains the Puppet classes required to provision RHEL OpenStack Platform. Only the new host is provisioned in accordance with its
assigned Compute role. The existing hosts are not reprovisioned.
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 t he Provisioning Process
The Red Hat Enterprise Linux OpenStack Platform installer has two main steps when provisioning each host:
Bu ild in g - 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 -o sp-i nstal l er stage. Configuring network interfaces.
Registering the system and attaching Red Hat product subscriptions. Installing Puppet for the configuration process.
Co n f ig u rat io n - 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 T ask page for your deployment, click Sho w mo re d etai l s under the progress bar on the
Deployment page. From there, click the D ynfl o w C o nso l e.
These D ynfl o w C o nso l e displays a combination of subtasks associated with your deployment. Knowing the functions of each subtask helps with determining the deployment stage. These subtasks are:
Act io n s::St ayp u f t ::Ho st ::Up d at e Updates a host's attributes.
Act io n s::St ayp u f t ::Ho st ::T rig g erPro visio n in g
Starts the provisioning process for a new host. This includes resetting the host and PXE booting to the provisioning templates assigned to the host.
Act io n s::St ayp u f t ::Ho st ::Wait Un t ilPro visio n ed
Waits until the host provisioning process completes. This item completes when the host finishes running through the kickstart provisioning template.
Act io n s::St ayp u f t ::Ho st ::Wait Un t ilRead y
Checks if a particular host is ready to accept SSH connections. This is so the installer can start the Puppet Agent on the host.
Act io n s::St ayp u f t ::Ho st ::Pu p p et Ru n
Waits until the Puppet Agent on the host completes configuration and sends a report. Act io n s::St ayp u f t ::Ho st ::Assert Rep o rt Su ccess
Checks if the host has any outstanding errors from the last Puppet Agent report.
9.2. T roubleshoot ing Issues when Building Host s
9.2.1. Reviewing Anaconda Logs
Host provisioning in a Red Hat Enterprise Linux OpenStack Platform environment uses Kickstart and anaco nd a to build the base operating system. This means the logs for the initial build are stored in /var/l o g /anaco nd a/ of each host. The log files in this directory show the host's entire build process and provide messages for any point of error. If a host fails to build, consult these log files to determine the causes of the failed build.
9.2.2. Checking Subscript ion Det ails and Inst alled Packages
Check if the host has successfully registered to the Red Hat Customer Portal and has the correct subscriptions attached:
# subscription-manager status
# subscription-manager list --consumed
# subscription-manager repos | grep "Enabled:.*1" -B3
Also check if the following packages were installed during the initial build process:
# yum list sos sos-plugins-openstack rhos-log-collector puppet rhel-osp- installer-client
If the hosts lacks the required subscription details or necessary packages after the build process completes, it means an error occurred when attempting to register your host and attach the relevant subscription pools. Check the build logs (see Section 9.1, “ Defining the Provisioning Process”) or restart the build process for the host (see Section 9.2.4, “ Rebuilding Hosts”) to see where the subscription management issues occur.
9.2.3. Edit ing Kickst art T emplat es
The Red Hat Enterprise Linux OpenStack Platform installer uses a set of Kickstart templates and snippets. These templates are located in Ho st s → Pro visio n in g T emp lat es.
The default template used for provisioning hosts is the Ki ckstart R HEL d efaul t template. The template follows standard Kickstart syntax. However, the template also allows certain variables including:
Ho st Paramet ers - These are custom values defined for each host and are inserted into the template using the following syntax:
<% @ host.params['time-zone'] %>
A full list of parameters is available on each host's P arameters tab.
T emp lat e Sn ip p et s - Snippets are template segments used in multiple templates. Using
snippets reduces the amount of replication across multiple provisioning templates. Insert snippets into a template using the following syntax:
<%= snippet 'kickstart_networking_setup' %>
Editing the default kickstart template provides a means of customizing the build process to workaround any issues that appear in the anaco nd a logs of a faulty build.
Warning
The default Kickstart template and associated snippets are designed and tested to provide a working Red Hat Enterprise Linux OpenStack Platform environment. Only edit the default Kickstart template if your encounter an error in the build process and you feel comfortable with resolving the error yourself. Perform such edits with caution as faults in the Kickstart template can cause the provisioning process to stop functioning.
Contact your Red Hat Technical Support representative if you require help with diagnosing and resolving build errors in the provisioning process.