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.
1. Proposed title of this feature request
Add some check for `fapolicyd` service in installer or foreman-maintain and fail it if the said service is running.
Or else provide the steps to properly configure fapolicyd so that It can allow satellite to work normally.
2. What is the nature and description of the request?
Add a preupgrde check for `fapolicyd` service in foreman-maintain and fail it if the said service is running.
Or else provide the steps to properly configure fapolicyd so that It can allow satellite to work normally.
3. Why does the customer need this? (List the business requirements here)
As can be seen in https://access.redhat.com/solutions/6970341 , 30+ customers got affected by this issue when they tried to install Satellite on a RHEL 8 system or upgrade a satellite, having fapolicyd service running.
2022-08-02 15:55:10 [DEBUG ] [configure] /Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]/unless: /usr/bin/rake:23:in `load': cannot load such file -- /usr/share/gems/gems/rake-13.0.1/exe/rake (LoadError)
The only way to complete the installation\upgrade is by stopping and disabling this service.
Since fapolicyd is considered a component of security hardening, I understand that it is not supported but we should detect it way before the actual installation or upgrade begins for a satellite or capsule.
4. How would the customer like to achieve this? (List the functional requirements here)
Via installer ( for installations ) or foreman-maintain ( for upgrades )
5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Installation of satellite or upgrade of a Satellite should be blocked if fapolicyd found to be enabled and running on the OS.
Many users also have requested to share the expected way to configure fapolicyd but I am assuming we would not support that for satellite.
6. Is there already an existing RFE upstream or in Red Hat Bugzilla?
No
I am aware of https://bugzilla.redhat.com/show_bug.cgi?id=2109740 but it does not explicitly cover fapolicyd aspect
7. Does the customer have any specific time-line dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
Satellite 6.14 or as soon as it's feasible
8. Is the sales team involved in this request and do they have any additional input?
NA
9. List any affected packages or components.
foreman-installer
rubygem-foreman_maintain
10. Would the customer be able to assist in testing this functionality if implemented?
RH support can