Workshop Exercise - Run OS Upgrade Jobs

Table of Contents



We are ready to start the upgrade phase of our RHEL in-place automation journey:

Automation approach workflow diagram with upgrade step highlighted

It is during this phase that the upgrade playbooks are executed using a workflow job template. The first playbook creates a snapshot that can be used for rolling back if anything goes wrong with the upgrade. After the snapshot is created, the second playbook uses the Leapp utility to perform the upgrade where the host is advanced to the new RHEL major version.

Step 1 - Launch the Upgrade Workflow Job Template

We are about to start the RHEL in-place upgrade of our pet application servers. The hosts will not be available for login or application access during the upgrade. When the upgrade is finished, the hosts will reboot under the newly upgraded RHEL major version.

Upgrades typically take less than an hour, although they can run for longer if there are applications that shutdown slowly or with bare metal hosts that have a long reboot cycle. The cloud instances provisioned for our workshop lab environment will upgrade fairly quickly as they are very lightweight compared to traditional enterprise app servers.

Step 2 - Learn More About Leapp

After launching the upgrade job, the AAP Web UI will navigate automatically to the workflow job output page of the job we just started. This job will take up to 20 minutes to finish, so let’s take this time to learn a little more about how the Leapp framework upgrades your OS to next RHEL major version.


In this exercise, we launched a workflow job template to create snapshots and start the upgrades of our pet app servers. We learned more about the Leapp framework to better understand what is happening as the RHEL OS is being upgraded.

In the next exercise, we’ll learn more about how snapshots work.


Previous Exercise - Next Exercise