AI-assisted Red Hat Enterprise Linux upgrades with Ansible

Major operating system (OS) upgrades do not have to mean weekend fire drills and manual guesswork. This checklist shows how Red Hat® Enterprise Linux® customers can prepare for AI-assisted upgrades using Red Hat Ansible® Automation Platform.

Fear around upgrades is rarely about version change—it is the risk of an unknown outage, where recovery is slow or manual. Automated workflows allow you to orchestrate the upgrade utility, enforcing snapshot-and-rollback safeguards across your organization’s infrastructure. Verify that the rollback is needed first, then commit the upgrade or restore the system without a scramble.

• Familiarize yourself with Leapp¹: Red Hat’s official command-line utility for major in-place Red Hat Enterprise Linux upgrades (such as Red Hat Enterprise Linux 7 to 8 or 8 to 9) that preserves data, settings, and software without wiping the system.
• Snapshot early: Create recoverable virtual machine (VM) or logical volume manager (LVM) snapshots before the Leapp tool performs in-place system upgrades from 1 major version of Red Hat Enterprise Linux to another.
• Automate workflows: Gate progress on post-upgrade checks (service health, kernel, and critical packages). If the check fails, stop the batch.
• Practice before production: Rehearse rollback in a non-production cohort.

Host-by-host upgrades do not scale, and playbooks that differ by team create uneven risk. Make in-place Red Hat Enterprise Linux upgrades into a repeatable service with Ansible Automation Platform.

• Create inventory cohorts: Group hosts by environment, dependency, or business criticality—then upgrade them in controlled waves.
• Use certified content: Run Red Hat Enterprise Linux upgrade content built with field-proven Leapp automation, not one-time scripts.
• Track your progress: Track pre-upgrade readiness and completion from a single automation management interface.

Unsupported OS versions expand attack surfaces and stretch compliance windows. Moving to a supported Red Hat Enterprise Linux standard reduces that exposure, while Ansible Automation Platform keeps the path governed with role-based access control (RBAC), credential management, and auditable job history.

• Reduce exposure: Prioritize upgrading older major versions, so security and lifecycle risk shrinks with each wave.
• Use RBAC to manage credentials: Separate who can plan, approve, and execute upgrades.
• Audit job history: Validate security and configuration outcomes after upgrade—verify certificates, check drift controls are applied properly, and review the list of required agents—before calling the wave done.

Rebuilds can reset debt, but are disruptive and slow for large organizations. An in-place upgrade is a practical path forward. This approach allows your teams to modernize on a supported OS without requiring a multi-year migration project.

• Find blockers early: Run Leapp pre-upgrade analysis to surface blockers (to identify incompatible packages, verify misconfigured repositories, and check configuration hazards) before scheduling downtime.
• Automate known remediations: Automate common remediations for agents and middleware so that each host is not a custom project.
• Preserve working configs: Treat the upgrade as a step toward standardization, then plan deeper application modernization.

Moving too quickly without governance can create unnecessary risk. AI-assisted planning with Ansible Automation Platform shortens preparation while deterministic automation executes a consistent pattern every time. 

• Snapshot your environment: Use automation intelligent assistant (formerly Red Hat Ansible Lightspeed intelligent assistant) for authoring playbooks, explaining complex code, and resolving playbook errors before deployment. 
• Upgrade: Consider adopting Model Context Protocol (MCP) within your automation platform. An MCP server securely connects your IT inventory to AI models, allowing AI to draft workflow steps.
• Validate, then commit: Review the recommended plan. Humans decide what and when, but Ansible Automation Platform can execute repeatably, with audit trails.

Senior administrators spend significant time identifying inhibitors. Pre-upgrade intelligence and AI-assisted triage can help IT administrators get that time back.

• Find blockers early: Run enterprise-wide Leapp assessments prior to an upgrade and categorize inhibitors before maintenance windows.
• Recommend remediations: Use AI-assisted analysis to recommend fixes and draft remediation playbooks for review. Avoid unsupervised production changes.
• Automate and re-run analysis: Optionally trigger remediations with Event-Driven Ansible when reports show known, approved inhibitors.