mrjoshuap / ansible-leapp

An Ansible role that attempts an inplace upgrade of EL7 to EL8 using LEAPP
GNU General Public License v2.0
15 stars 12 forks source link
ansible-role leapp playbook

ansible-leapp

This Ansible role attempts to perform an automated in-place upgrade of EL based systems, primarily Red Hat Enterprise Linux.

It performs the following high level tasks:

By default, this role will not perform the actual upgrade. It is intended to prepare the system and generate a preupgrade report that should be reviewed. If you're feeling lucky, you can also have it attempt to perform the upgrade.

TODO

References

I used the following docs for reference:

Role Variables

Variables that modify the behavior of this role are declared in defaults/main.yml

# Provide a list of repository IDs that exist in /etc/yum.repos.d
# Default []
leapp_custom_repositories: []

# specify a grub device, generally not required for most installations
leapp_grub_device: '/boot'

# Skip Red Hat Subscription Manager? Default no
leapp_skip_rhsm: no

# Skip the validation pre-flight checks? Default no
leapp_skip_validate: no

# Skip the prepare tasks? Default no
leapp_skip_prepare: no

# Skip cockpit installation? Default no
leapp_skip_prepare_cockpit_install: no

# Skip package installation?  Default no
leapp_skip_prepare_package_install: no

# Skip actual package updates?  Default yes
leapp_skip_prepare_update: yes

# Skip reboot after changes to package updates?  Default no
leapp_skip_prepare_update_reboot: no

# Skip the leapp preupgrade? Default yes
leapp_skip_preupgrade: yes

# Skip removing previous reports?  Defaults no
leapp_skip_preupgrade_cleanup: no

# Skip remediate of common issues?  Defaults yes
leapp_skip_remediate: yes

# Skip the actual leapp upgrade? Default yes
leapp_skip_upgrade: yes

# How long to wait (in seconds) for reboot after upgrade? Default 1200
leapp_reboot_timeout: 1200

Dependencies

There are no dependencies to use this role, however, this role assumes you have implemented a standard operating environment that provides:

Additionally, you must also download the additional required data files (RPM package changes and RPM repository mapping) attached to the Knowledgebase Article and place it in the 'files' directory in the same directory as the playbook including this role.

Example Playbook

The following is a simple playbook that will perform the default behaviors up to performing the actual upgrade:

---

- name: Perform an in-place upgrade of a EL System
  hosts: all
  become: yes

  vars:
    # Provide a list of repository IDs that exist in /etc/yum.repos.d
    # Default []
    leapp_custom_repositories: []

    # Skip Red Hat Subscription Manager? Default no
    leapp_skip_rhsm: no

    # Skip the validation pre-flight checks? Default no
    leapp_skip_validate: no

    # Skip the prepare tasks? Default no
    leapp_skip_prepare: no

    # Skip cockpit installation? Default no
    leapp_skip_prepare_cockpit_install: no

    # Skip package installation?  Default no
    leapp_skip_prepare_package_install: no

    # Skip actual package updates?  Default yes
    leapp_skip_prepare_update: yes

    # Skip the leapp preupgrade? Default no
    leapp_skip_preupgrade: no

    # Skip removing previous reports?  Defaults no
    leapp_skip_preupgrade_cleanup: no

    # Skip the actual leapp upgrade? Default yes
    leapp_skip_upgrade: yes

    # How long to wait (in seconds) for reboot after upgrade? Default 1200
    leapp_reboot_timeout: 1200

  roles:
    - mrjoshuap.leapp

License

GPL-2.0-or-later

Author Information

Joshua Preston is a solution architect with Red Hat, specializing in Platform and Management technologies.