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.

Bug 2223931

Summary: In-place upgrade post-upgrade steps fail due to foreman-protector
Product: Red Hat Satellite Reporter: Julio Entrena Perez <jentrena>
Component: UpgradesAssignee: Akshay Gadhave <agadhave>
Status: CLOSED CURRENTRELEASE QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.11.5CC: agadhave, ehelms, jbhatia, mdolezel, mjivraja, mportman, rlavi, saydas, sjalgaon
Target Milestone: UnspecifiedKeywords: Documentation, Triaged
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-28 05:52:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Julio Entrena Perez 2023-07-19 10:01:53 UTC 
Description of problem:
"Chapter 4. Upgrading Satellite or Capsule to Red Hat Enterprise Linux 8 In-Place Using Leapp" in its step 10 points customers to post-upgrade tasks covered in RHEL 8 in-place upgrades documents.

These steps involve yum commands that fail due to foreman-protector blocking access to all content.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Follow link in step 10 that points to "Chapter 7. Performing post-upgrade tasks" of the "Upgrading from RHEL 7 to RHEL 8" document.
2. Attempt the yum commands
3.

Actual results:
# dnf reinstall -y kernel-core-$(uname -r)
Updating Subscription Management repositories.

This system is registered with an entitlement server, but is not receiving updates. You can use subscription-manager to assign subscriptions.

Last metadata expiration check: 2:03:09 ago on Tue Jul 11 14:03:37 2023.
Reading Foreman protector configuration
Excluded total: 43130

WARNING: Excluding 43130 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.15.1.el8_8.x86_64 not available.
Error: No packages marked for reinstall.

Expected results:
Step 10 of "Chapter 4. Upgrading Satellite or Capsule to Red Hat Enterprise Linux 8 In-Place Using Leapp" should suggest users to temporarily disable foreman-protector before jumping to "Chapter 7. Performing post-upgrade tasks" or to explicitly disable foreman-protector in every yum/dnf command.

Additional info:
Comment 19 Zuzana Lena Ansorgova 2023-08-29 10:51:47 UTC 
*** Bug 2233520 has been marked as a duplicate of this bug. ***