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.

foreman-maintain is going to need to detect and handle specific conditions when it is managing a Satellite and Capsule running on RHEL 8, examples:

 * enable/disable the correct RHEL8 repositories
 * possible different service names for restarting services
 * different file locations for backup/restore
 * different OS level commands for firewall and other routines

Created redmine issue https://projects.theforeman.org/issues/27511 from this bug

Upstream bug assigned to apatel

Verified.

Tested on Satellite 6.11.0 Snap 22.0
Version: rubygem-foreman_maintain-1.0.10-1.el8sat.noarch

Steps:
1. # foreman-maintain --help

Observation, 
In Satellite 6.11, foreman-maintain works on both RHEL7 and RHEL8, the main difference being for Backup/Restore where EL7 will use iptables while EL8 will use nftables (which will be preinstalled), as well as all differences like repositories and package manager between EL7 and EL8 are handled correctly.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Satellite 6.11 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5498