-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
rhel-9.6, rhel-9.7
On systems with ARM architecture are present 4k and 64k kernels (note that possibly there is already now also the realtime kernel as well!). When upgrading the system, the 64k kernel is not correctly identified which has some negative side effects - mainly during phases after the DNF transaction execution - including problem with boting into incorrect kernel after the upgrade.
The problem is that current kernel related models and library recognize only ordinary and realtime kernels. This needs to be extended to cover the 64k kernel on ARM systems as well. See the result of investigation in RHELMISC-16032 for additional details.
Note that AC can be still little bit updated based on answers we receive from kernel team.
Expected actions:
- update the kernel shared library in the system_upgrade_common repository
to include also 64k kernel type - adjust the KernelInfo model
- detect properly 64k kernel on ARM architecture if booted
- adjust the logic in the actors in a similar way as applied for the realtime
kernel, just in this case cover 64k kernel - 64k kernel can be detected based on the `+64k` suffix in the `uname_r` string
AC:
- all kernels are properly identified (4k kernel stays identified as the ordinary one)
- after the upgrade, system is booted into the same type of kernel ason the source system
- IOW, the 64k kernel is handled in a similar way as applied for the realtime kernel