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 the user has performed leapp upgrade on Satellite-6.11 and Satellite OS has been successfully upgraded to RHEL-8 using below documentation:
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html/upgrading_and_updating_red_hat_satellite/upgrading-satellite-or-proxy-in-place-using-leapp_upgrade-guide
The point 10 in above documentation says:
10. Complete these procedures in Upgrading from RHEL 7 to RHEL 8:
i. Verifying the post-upgrade state of the RHEL 8 system
ii. Performing post-upgrade tasks
The point "ii. Performing post-upgrade tasks" redirects user to RHEL documentation:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/upgrading_from_rhel_7_to_rhel_8/performing-post-upgrade-tasks-rhel-7-to-rhel-8_upgrading-from-rhel-7-to-rhel-8#doc-wrapper
The Point 5(ii) in RHEL documentation asks user to run below command on Satellite.
ii. Reinstall the current kernel to recover the rescue kernel and related initial RAM disk:
# dnf reinstall -y kernel-core-$(uname -r)
The above command fails on Satellite due to foreman protector package lock on Satellite.
~~~
# dnf reinstall kernel-core.x86_64
Updating Subscription Management repositories.
Last metadata expiration check: 2:36:12 ago on Mon 21 Aug 2023 02:47:32 PM CEST.
Reading Foreman protector configuration
*** Excluded total: 43573
WARNING: Excluding 43573 packages due to foreman-protector.
Use foreman-maintain packages install/update <package>
to safely install packages without restrictions.
Use foreman-maintain upgrade run for full upgrade.
Installed package kernel-core-4.18.0-477.21.1.el8_8.x86_64 not available.
Error: No packages marked for reinstall.
~~~
Version-Release number of selected component (if applicable): Leapp Post Upgrade Tasks on Satellite-6.11
How reproducible: Always
Expected results: Either the command should run successfully or there should be a Note which should ask user to unlock the packages on Satellite and then run "dnf reinstall" command.
Comment 5Zuzana Lena Ansorgova
2023-08-29 10:51:47 UTC
*** This bug has been marked as a duplicate of bug 2223931 ***
Description of problem: After the user has performed leapp upgrade on Satellite-6.11 and Satellite OS has been successfully upgraded to RHEL-8 using below documentation: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html/upgrading_and_updating_red_hat_satellite/upgrading-satellite-or-proxy-in-place-using-leapp_upgrade-guide The point 10 in above documentation says: 10. Complete these procedures in Upgrading from RHEL 7 to RHEL 8: i. Verifying the post-upgrade state of the RHEL 8 system ii. Performing post-upgrade tasks The point "ii. Performing post-upgrade tasks" redirects user to RHEL documentation: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/upgrading_from_rhel_7_to_rhel_8/performing-post-upgrade-tasks-rhel-7-to-rhel-8_upgrading-from-rhel-7-to-rhel-8#doc-wrapper The Point 5(ii) in RHEL documentation asks user to run below command on Satellite. ii. Reinstall the current kernel to recover the rescue kernel and related initial RAM disk: # dnf reinstall -y kernel-core-$(uname -r) The above command fails on Satellite due to foreman protector package lock on Satellite. ~~~ # dnf reinstall kernel-core.x86_64 Updating Subscription Management repositories. Last metadata expiration check: 2:36:12 ago on Mon 21 Aug 2023 02:47:32 PM CEST. Reading Foreman protector configuration *** Excluded total: 43573 WARNING: Excluding 43573 packages due to foreman-protector. Use foreman-maintain packages install/update <package> to safely install packages without restrictions. Use foreman-maintain upgrade run for full upgrade. Installed package kernel-core-4.18.0-477.21.1.el8_8.x86_64 not available. Error: No packages marked for reinstall. ~~~ Version-Release number of selected component (if applicable): Leapp Post Upgrade Tasks on Satellite-6.11 How reproducible: Always Expected results: Either the command should run successfully or there should be a Note which should ask user to unlock the packages on Satellite and then run "dnf reinstall" command.