
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 5,151 Views
Hi,
Could anyone give some insight on what is the right upgrade(inplace) path - from RHEL8.2 to RHEL9.3.
Thanks
Upendar
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 4,679 Views
@r_upendar Thanks for reaching out.
You can refer the links, they should help you with your requirements.
Regards,
Wasim


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 4,642 Views
You won't be able to direclty upgrade from 8.2 to 9.3. To use the leapp tool, you'll first have to update your RHEL8 system to current. So your path looks more like:
8.2 -> 8.9 (using dnf update)
8.9 -> 9.3 (using leapp)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 4,601 Views
@r_upendar Thanks for reaching out !
Currently, it is possible to perform an in-place upgrade from the following source RHEL 8 minor versions to the following target RHEL 9 minor versions:
As @Scott mentioned use leapp tool to upgrade from RHEL 8.9 to RHEL 9.3
Refer here for the same : https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/upgrading_from_rhel_8_...
For upgrading RHEL 8.2 to RHEL 8.9 use dnf tool to upgrade it ( Don forget to use dnf versionlock clear to clear the specific package version lock , if used earlier ).

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 3,126 Views
Thank you so much @Wasim_Raja @Scott @Chetan_Tiwary_ .
When an attempt was made to upgrade the minor version from RHEL 8.2 to 8.8 and while doing the dnf update, the update process was stuck at the stage: "Running scriptlet: systemd-239-74.el8_8.x86_64". When the system is rebooted, the boot process was freezed at systemd and we see errors similar to the following on the console:
systemd[1]: Freezing execution
The advisory: https://access.redhat.com/errata/RHSA-2020:5608 helped resolve the issue.


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 3,095 Views
If you update less frequently, there's a lot less likelihood that you'll run into an issue like this. Red Hat does a TON of testing to ensure upgrading to a new minor-release is smooth from the previous minor release, e.g. 8.2->8.3 or 8.3->8.4
We also do alot of testing to ensure that upgrades between Extended Update Releases (EUS) goes smoothly, e.g. 8.2->8.4 or 8.4->8.6
However, we really don't do testing for large gaps of minor release updates, like in your case 8.2->8.8. Building more frequent updates into your practices, or using EUS (included in x86_64 RHEL premium subs) to stay on releases for up to 2 years, then upgrading to the next EUS release, even numbered minor releases, will drastically reduce the chances for unaccounted for weirdness when applying updates to your machines.
-STM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 4,680 Views
@r_upendar Thanks for reaching out.
You can refer the links, they should help you with your requirements.
Regards,
Wasim


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 4,643 Views
You won't be able to direclty upgrade from 8.2 to 9.3. To use the leapp tool, you'll first have to update your RHEL8 system to current. So your path looks more like:
8.2 -> 8.9 (using dnf update)
8.9 -> 9.3 (using leapp)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 4,633 Views
@Scott Thank you for sharing!!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 4,600 Views
Thanks @Scott +1

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 4,602 Views
@r_upendar Thanks for reaching out !
Currently, it is possible to perform an in-place upgrade from the following source RHEL 8 minor versions to the following target RHEL 9 minor versions:
As @Scott mentioned use leapp tool to upgrade from RHEL 8.9 to RHEL 9.3
Refer here for the same : https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/upgrading_from_rhel_8_...
For upgrading RHEL 8.2 to RHEL 8.9 use dnf tool to upgrade it ( Don forget to use dnf versionlock clear to clear the specific package version lock , if used earlier ).

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 3,127 Views
Thank you so much @Wasim_Raja @Scott @Chetan_Tiwary_ .
When an attempt was made to upgrade the minor version from RHEL 8.2 to 8.8 and while doing the dnf update, the update process was stuck at the stage: "Running scriptlet: systemd-239-74.el8_8.x86_64". When the system is rebooted, the boot process was freezed at systemd and we see errors similar to the following on the console:
systemd[1]: Freezing execution
The advisory: https://access.redhat.com/errata/RHSA-2020:5608 helped resolve the issue.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 3,101 Views
@r_upendar Glad to hear that!


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 3,096 Views
If you update less frequently, there's a lot less likelihood that you'll run into an issue like this. Red Hat does a TON of testing to ensure upgrading to a new minor-release is smooth from the previous minor release, e.g. 8.2->8.3 or 8.3->8.4
We also do alot of testing to ensure that upgrades between Extended Update Releases (EUS) goes smoothly, e.g. 8.2->8.4 or 8.4->8.6
However, we really don't do testing for large gaps of minor release updates, like in your case 8.2->8.8. Building more frequent updates into your practices, or using EUS (included in x86_64 RHEL premium subs) to stay on releases for up to 2 years, then upgrading to the next EUS release, even numbered minor releases, will drastically reduce the chances for unaccounted for weirdness when applying updates to your machines.
-STM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 2,947 Views
While doing the major version upgrade from RHEL 8.10 to RHEL 9.4 using the leap upgrade utility, it has hit the errors reported below:
And while doing the major version upgrade using the leap upgrade, it's throwing a different error, now as reported in https://access.redhat.com/discussions/7049671. Could you please help upgrade the major ver
2024-10-15 00:20:25.550 ERROR PID: 32385 leapp.workflow.TargetTransactionFactsCollection: Actor target_userspace_creator has crashed: Traceback
(most recent call last):
File "/usr/lib/python3.6/site-packages/leapp/repository/actor_definition.py", line 74, in _do_run
actor_instance.run(*args, **kwargs)
File "/usr/lib/python3.6/site-packages/leapp/actors/__init__.py", line 289, in run
self.process(*args)
File "/etc/leapp/repos.d/system_upgrade/common/actors/targetuserspacecreator/actor.py", line 58, in process
userspacegen.perform()
File "/usr/lib/python3.6/site-packages/leapp/utils/deprecation.py", line 42, in process_wrapper
return target_item(*args, **kwargs)
File "/etc/leapp/repos.d/system_upgrade/common/actors/targetuserspacecreator/libraries/userspacegen.py", line 1246, in perform
_create_target_userspace(context, indata, indata.packages, indata.files, target_repoids)
File "/etc/leapp/repos.d/system_upgrade/common/actors/targetuserspacecreator/libraries/userspacegen.py", line 1108, in _create_target_userspace
_prep_repository_access(context, target_path)
File "/etc/leapp/repos.d/system_upgrade/common/actors/targetuserspacecreator/libraries/userspacegen.py", line 629, in _prep_repository_access
run(["chroot", target_userspace, "/bin/bash", "-c", "su - -c update-ca-trust"])
File "/usr/lib/python3.6/site-packages/leapp/libraries/stdlib/__init__.py", line 192, in run
result=result
leapp.libraries.stdlib.CalledProcessError: Command ['chroot', '/var/lib/leapp/el9userspace', '/bin/bash', '-c', 'su - -c update-ca-trust'] failed with exit code 127.