Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
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
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.