Bug 2219539 - Leapp Preupgrade job template get executed with Inhibitor "Newest installed kernel not in use"
Summary: Leapp Preupgrade job template get executed with Inhibitor "Newest installed k...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Leapp integration
Version: 6.14.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: visawant
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-04 08:44 UTC by visawant
Modified: 2023-07-25 12:09 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OAMG-9374 0 None None None 2023-07-17 10:34:38 UTC
Red Hat Issue Tracker SAT-18781 0 None None None 2023-07-04 11:54:28 UTC

Description visawant 2023-07-04 08:44:00 UTC
Description of problem: After running leapp preupgrade job template, /var/log/leapp/leapp-report.txt shows Inhibitor "Newest installed kernel not in use".
It means in order to run leapp-preupgrade template host need to reboot manually because this inhibitor is not fixable.


Version-Release number of selected component (if applicable):
Satellite 6.14.0
Leapp: 0.18.0-1.el8_8.2
Kernel: 4.18.0-477.13.1.el8_8.x86_64

How reproducible:
Not always, it happens sometimes

Steps to Reproduce:
1. Enable RHEL-8.8 BaseOS & AppStream repos, register rhel 8.8 host with satellite
2. Set rhel 8.8 release using "#subscription-manager release --set 8.8"
3. execute "#yum update -y" on host
4. install leapp tool using "yum install leapp-upgrade -y"
5. Run job template name "Run preupgrade via Leapp" and observe 'Leapp preupgrade report'

Actual results:
Job template 'Leapp-preupgrade' run successfully and Leapp preupgrade reports shows inhibitor "Newest installed kernel not in use"

Expected results:
Job template 'Leapp-preupgrade' run successfully and there should not be any inhibitor with High Risk Factor present.

Additional info:
Current kernel running version-
[root@ip-fqdn ~]# uname -r
4.18.0-477.13.1.el8_8.x86_64

available kernel versions-
# rpm -qa kernel
kernel-4.18.0-477.15.1.el8_8.x86_64
kernel-4.18.0-477.13.1.el8_8.x86_64
kernel-4.18.0-477.10.1.el8_8.x86_64

available kernel-core versions-
# rpm -qa kernel-core
kernel-core-4.18.0-477.10.1.el8_8.x86_64
kernel-core-4.18.0-477.15.1.el8_8.x86_64
kernel-core-4.18.0-477.13.1.el8_8.x86_64

In detail kernel-core
http://pastebin.test.redhat.com/1104099

Comment 2 visawant 2023-07-04 08:57:08 UTC
As per discussion with the-upgrade QE, 
- Leapp should run only when newly installed kernel is running (which is 4.18.0-477.15.1.el8_8.x86_64) and currently running kernel is 4.18.0-477.13.1.el8_8.x86_64
- In rhel-upgrade teams internal playbook, they have a specific step "check kernel version and reboot into the latest if needed" that is executed before running Leapp


Note You need to log in before you can comment on or make changes to this bug.