3.3. Configuring the upgrade from RHEL 9.7 to RHEL 10.1 with LiveMode
LiveMode is an alternative method of preparing and booting to the upgrade environment when upgrading from RHEL 9.7 to RHEL 10.1 on the 64-bit Intel architecture. LiveMode uses the standard booting process. The standard booting process can prevent or help diagnose certain problems that occur during the upgrade, such as issues related to the storage initialization. Note that LiveMode requires approximately 700 MB of additional disk space to create and store the upgrade environment before the reboot.
LiveMode is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.
When using LiveMode, you can also configure the upgrade experience beyond the default specifications. This can be useful when troubleshooting during the upgrade process or if you want to view the upgrade’s progress by using an SSH connection.
If you are using LiveMode without any modifications to the default settings, you do not need to complete any preparation steps for LiveMode before the upgrade. If you want to change the default specifications, you must create and modify a YAML file.
Procedure
-
If you want to modify LiveMode’s default specifications, create a YAML file in the
/etc/leapp/actor_conf.d/file, for examplelivemode.yaml. Enter the desired LiveMode configuration into the YAML file.
Expand 표 3.1. LiveMode configuration Configuration field Value type Default Description additional_packages
List[str]
[]
Additional packages to be installed into the upgrade image.
autostart_upgrade_after_reboot
bool
True
If set to
True, the upgrade starts automatically after the reboot. Otherwise, a manual trigger is required.capture_strace_info_into
str
''
If set to a non-empty string,
leappis executed understraceand results are stored within the provided file path.dracut_network
str
''
Dracut network arguments. Required if the `url_to_load_squashfs_`from option is set to a non-empty string.
setup_network_manager
bool
False
If set to
False, the Leapp tool enables Network Manager in the upgrade image.setup_opensshd_using_auth_keys
str
''
If set to a non-empty string,
opensshdaemon is set up within the upgrade image using the provided authorized keys file.setup_passwordless_root
bool
False
If set to
True, the root account of the upgrade image has an empty password. Use with caution.squashfs_image_path
str
/var/lib/leapp/live-upgrade.img
Desired location of the upgrade image of the minimal target system.
url_to_load_squashfs_image_from
str
''
URL of the desired upgrade image.
The following is an example of a
/etc/leapp/actor_conf.d/livemode.yamlfile:livemode: additional_packages : [ vim ] autostart_upgrade_after_reboot : false setup_network_manager : true setup_opensshd_using_auth_keys : /root/.ssh/authorized_keysThe example file results in the following actions:
-
The Leapp utility installs the
vimpackage into the upgrade environment. - The upgrade does not start automatically after reboot. You must manually restart it. This allows you to manually inspect the system and verify that the upgrade finished as expected and the system is ready for use before starting.
- The Leapp utility attempts to enable NetworkManager inside the upgrade environment by using the source system’s network profiles.
-
The Leapp utility enables the
opensshdservice. If the system establishes network access successfully, you can use SSH to log in to the upgrade environment by using the root account and interact with the system.
-
The Leapp utility installs the