How to Upgrade AlmaLinux 9 to AlmaLinux 10

AlmaLinux 10 represents a significant leap forward in enterprise Linux distribution technology, delivering enhanced security features, improved performance optimizations, and expanded hardware compatibility. For system administrators managing AlmaLinux 9 environments, upgrading to this latest version offers access to cutting-edge capabilities without the complexity and downtime associated with fresh installations.

The upgrade process leverages the powerful ELevate project, an innovative solution that has successfully facilitated over 500,000 device upgrades since its introduction in 2021. This comprehensive guide provides detailed, step-by-step instructions for safely migrating your AlmaLinux 9 systems to AlmaLinux 10, ensuring minimal disruption to your operations while maximizing the benefits of the newest release.

Whether you’re managing a single server or an entire enterprise infrastructure, this guide addresses the critical considerations, potential challenges, and best practices necessary for a successful upgrade. From initial preparation through post-upgrade optimization, every aspect of the migration process is covered with practical examples and expert recommendations.

Understanding the ELevate Project Foundation

The ELevate project stands as a cornerstone innovation in RHEL-based Linux distribution upgrades. Developed to address the traditional challenges of major version migrations, ELevate provides an automated, reliable pathway for upgrading between different operating system versions without requiring complete system reinstallation.

ELevate Project Architecture

ELevate utilizes the open-source Leapp framework combined with specialized data libraries to automate complex upgrade procedures. The Leapp utility performs comprehensive system analysis, identifies potential compatibility issues, and orchestrates the upgrade process while maintaining system integrity throughout the transition.

The project’s success stems from its methodical approach to handling package dependencies, configuration file migrations, and service continuity. Since 2021, the ELevate ecosystem has expanded to support multiple RHEL-based distributions, including AlmaLinux, Rocky Linux, CentOS, and Oracle Linux.

Current Development Status

AlmaLinux 10 upgrades are currently in the testing and development phase. While the upgrade path is functional and has been successfully tested across numerous configurations, it’s not yet recommended for production environments. The development team focuses on delivering robust leapp-data and leapp-repository packages specifically optimized for AlmaLinux 10 migrations.

System administrators should thoroughly test the upgrade process in non-production environments before considering production deployments. The testing phase allows for comprehensive evaluation of application compatibility, performance characteristics, and operational stability.

Prerequisites and System Preparation

Successful AlmaLinux 9 to AlmaLinux 10 upgrades require careful preparation and adherence to specific prerequisites. These foundational steps ensure optimal upgrade outcomes and minimize potential complications.

Essential System Requirements

Before initiating the upgrade process, verify your current AlmaLinux 9 installation meets all necessary requirements:

• Current System Verification: Confirm your system is running a fully updated AlmaLinux 9 installation. Execute the following command to check your current OS version:

cat /etc/os-release

The output should display AlmaLinux 9.x with appropriate version identifiers.

• Hardware Compatibility Assessment: Ensure adequate system resources are available for the upgrade process. Minimum requirements include sufficient disk space for package downloads and temporary files, stable network connectivity for repository access, and adequate RAM to support the upgrade process without performance degradation.
• Network Connectivity Requirements: Stable internet connectivity is essential for downloading upgrade packages and accessing ELevate repositories. Verify firewall configurations allow access to required repositories and ensure DNS resolution functions correctly.

Critical Backup Procedures

Comprehensive system backups represent the most crucial preparatory step for any major upgrade. Create complete system backups including:

• Full System Backup: Implement comprehensive backup strategies covering all critical data, configuration files, and system states. Consider using tools like rsync, tar, or dedicated backup solutions to create complete system images.
• Database and Application Data: Separately backup all database contents, application data, and user files. Test backup integrity by performing restoration procedures in isolated environments.
• Configuration File Preservation: Document and backup critical configuration files, including network settings, service configurations, and custom application settings. This documentation proves invaluable for troubleshooting and rollback scenarios.

Production Environment Considerations

Upgrading production systems requires additional planning and risk mitigation strategies:

• Testing Environment Setup: Establish representative testing environments that mirror production configurations. Perform complete upgrade procedures in testing environments before attempting production upgrades.
• Maintenance Window Planning: Schedule appropriate maintenance windows considering the upgrade duration and potential complications. Communicate planned downtime to stakeholders and prepare contingency plans for extended maintenance periods.
• Rollback Strategy Development: Develop comprehensive rollback procedures including system restoration from backups, service restoration priorities, and communication protocols for stakeholder updates.

Step-by-Step Upgrade Process

The AlmaLinux 9 to AlmaLinux 10 upgrade process follows a systematic approach ensuring thorough preparation, careful execution, and comprehensive verification.

System Updates and Preparation

Begin the upgrade process by ensuring your AlmaLinux 9 system contains the latest package updates:

sudo dnf update -y
sudo dnf clean all
sudo reboot

After the reboot, verify your system’s current state and ensure all services function correctly. This preparation step eliminates potential package conflicts and ensures the upgrade process begins from a stable system state.

Installing ELevate Components

The next phase involves installing the ELevate repository configuration and required upgrade tools:

Repository Configuration: Install the ELevate NG repository configuration for AlmaLinux 9:

sudo curl -o /etc/yum.repos.d/elevate-ng.repo https://repo.almalinux.org/elevate/testing/elevate-ng-el$(rpm -E %rhel).repo

Security Key Import: Import the ELevate GPG key to ensure package authenticity:

sudo rpm --import https://repo.almalinux.org/elevate/RPM-GPG-KEY-ELevate

Package Installation: Install the required Leapp upgrade tools and AlmaLinux-specific data packages:

sudo yum install -y leapp-upgrade leapp-data-almalinux

These packages provide the core functionality for analyzing your system, identifying upgrade requirements, and executing the migration process.

Pre-upgrade Analysis and Validation

Before proceeding with the actual upgrade, perform comprehensive system analysis using Leapp’s preupgrade functionality:

sudo leapp preupgrade

This command initiates detailed system scanning, generating comprehensive reports about potential upgrade issues, required fixes, and recommended actions. The analysis phase creates several important files:

Leapp Report Analysis: Review the generated /var/log/leapp/leapp-report.txt file carefully. This report contains critical information about:

• System compatibility issues requiring resolution
• Package conflicts that need addressing
• Configuration changes necessary for successful upgrade
• Security considerations and recommendations

Answer File Requirements: In certain configurations, Leapp generates an /var/log/leapp/answerfile containing true/false questions requiring administrator input. These questions typically address specific configuration choices or policy decisions affecting the upgrade process.

Inhibitor Resolution: Address all identified inhibitors before proceeding with the upgrade. Common inhibitors include deprecated network configurations, incompatible kernel modules, or conflicting package versions.

Executing the Upgrade Process

Once all preupgrade checks pass successfully and inhibitors are resolved, proceed with the actual upgrade:

sudo leapp upgrade

This command initiates the comprehensive upgrade process, including:

Package Download and Installation: Leapp downloads all necessary packages for AlmaLinux 10, replacing existing AlmaLinux 9 components while preserving system configurations and user data.

System Reboot and Continuation: After package installation completes, reboot the system to continue the upgrade process:

sudo reboot

During the reboot process, a special GRUB entry labeled “ELevate-Upgrade-Initramfs” appears, automatically initiating the final upgrade phases. This process may require significant time depending on system configuration and hardware specifications.

Boot Process Monitoring: Ensure console access to monitor the upgrade progress. The system automatically proceeds through various upgrade phases, including configuration migrations, service updates, and final system optimization.

Post-Upgrade Verification and Optimization

After successful completion of the upgrade process, comprehensive verification ensures system stability and optimal performance.

Initial System Validation

Verify successful upgrade completion by checking the system’s current operating system version:

cat /etc/redhat-release
# OR
cat /etc/os-release
# OR
neofetch

These commands confirm the system now runs AlmaLinux 10 with appropriate version identifiers.

Package Cleanup and Management

Remove residual packages from the previous AlmaLinux 9 installation:

rpm -qa | grep el9

This command identifies remaining AlmaLinux 9 packages that may require manual removal or updating. Additionally, clean up ELevate-specific packages no longer needed:

rpm -qa | grep elevate
rpm -qa | grep leapp

Consider removing these packages using appropriate package management commands, ensuring system cleanliness and optimal performance.

System Configuration Updates

Update system configurations to reflect the new AlmaLinux 10 environment:

Hostname Updates: Modify the hostname to reflect the updated system:

sudo hostnamectl set-hostname AlmaLinux-10.local

Service Verification: Verify all critical services function correctly in the new environment. Check service status, configuration validity, and performance characteristics.

Log Review: Examine upgrade logs for any warnings or issues requiring attention:

sudo cat /var/log/leapp/leapp-report.txt
sudo cat /var/log/leapp/leapp-upgrade.log

These logs provide detailed information about the upgrade process, including any issues encountered and their resolutions.

Troubleshooting Common Issues

Despite careful preparation, upgrade processes may encounter various challenges requiring systematic troubleshooting approaches.

Pre-upgrade Issue Resolution

Common preupgrade problems include package dependency conflicts, insufficient disk space, and configuration incompatibilities. Address these issues systematically:

• Dependency Conflicts: Resolve package dependency issues by updating conflicting packages or removing incompatible software before attempting the upgrade.
• Storage Space Issues: Ensure adequate disk space for package downloads and temporary files. Clean unnecessary files and consider expanding storage if required.
• Network Configuration Problems: Address deprecated network configurations, particularly DHCP plugin issues common in progressively upgraded systems.

Upgrade Process Complications

During the upgrade process, potential issues may include boot failures, package installation errors, or service startup problems:

• Boot Recovery Procedures: If the system fails to boot after upgrade, utilize console access to diagnose and resolve GRUB-related issues or kernel problems.
• Package Installation Failures: Address package installation errors by reviewing upgrade logs, resolving dependency conflicts, and ensuring repository accessibility.
• Service Startup Issues: Diagnose and resolve service startup problems by examining service logs, updating configurations, and addressing compatibility issues.

Post-upgrade Problem Resolution

After successful upgrade completion, address any remaining issues affecting system functionality:

• Application Compatibility: Test all critical applications for compatibility with AlmaLinux 10, updating or replacing incompatible software as necessary.
• Performance Optimization: Monitor system performance and optimize configurations for optimal AlmaLinux 10 operation.
• Security Configuration: Review and update security configurations, ensuring all policies and settings remain appropriate for the new environment.

Best Practices and Expert Recommendations

Successful AlmaLinux upgrades rely on adherence to established best practices and expert-recommended procedures.

Planning and Preparation Excellence

Effective upgrade planning encompasses comprehensive testing, documentation, and risk assessment:

• Comprehensive Testing: Perform complete upgrade procedures in representative testing environments before attempting production upgrades. Document all findings and develop resolution procedures for identified issues.
• Change Management: Implement formal change management processes including approval workflows, rollback procedures, and communication protocols.
• Documentation Standards: Maintain detailed documentation covering upgrade procedures, configuration changes, and lessons learned for future reference.

Ongoing Maintenance Strategies

Post-upgrade success requires ongoing attention to system maintenance and optimization:

• Regular Monitoring: Implement comprehensive monitoring covering system performance, security status, and application functionality.
• Update Management: Establish systematic approaches to managing AlmaLinux 10 updates, security patches, and configuration changes.
• Performance Optimization: Continuously monitor and optimize system performance, addressing any degradation or inefficiencies.

Beta Release Considerations and Future Planning

Understanding the current development status helps set appropriate expectations and planning considerations.

Current Beta Status Limitations

AlmaLinux 10 upgrades currently exist in beta status with specific limitations:

• Production Environment Restrictions: Beta releases are not recommended for production environments due to potential stability issues and ongoing development changes.
• Testing and Feedback: The beta phase focuses on identifying and resolving issues through community testing and feedback.
• Support Considerations: Beta releases may have limited support options compared to stable releases.

Stable Release Migration Planning

Prepare for eventual migration to stable AlmaLinux 10 releases:

• Timeline Monitoring: Stay informed about stable release development timelines and availability announcements.
• Migration Procedures: Develop procedures for migrating from beta to stable releases when available.
• Testing Continuation: Continue testing beta releases to ensure smooth transitions to stable versions.