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.
DescriptionBrad Buckingham
2021-08-06 20:44:15 UTC
Description of problem:
As part of the Satellite 6.9 Pulp 3 High-Touch Beta, it several SELinux alerts were triggered. This bugzilla will reference them in a private comment as they were shared.
During this HTB, a Satellite 6.9 instance went through the process of migration to Pulp 3, a switchover to Pulp 3 was performed and content management workflows executed.
Version-Release number of selected component (if applicable):
6.9.1
In regard to
#============= foreman_rails_t ==============
allow foreman_rails_t systemd_systemctl_exec_t:file getattr;
I am unable to reproduce this one, however, it looks like the app is preparing for executing systemctl command which is not something we will allow in SELinux. I believe this was fixed recently: https://github.com/Katello/katello/pull/9403/files which was fixed in Katello 3.18.4 https://projects.theforeman.org/issues/32787
In 6.9 I still see 3.18.1 tho, filing new BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2000424
The rest is Pulp which I am flipping over to the Pulp team.
Comment 19pulp-infra@redhat.com
2021-09-29 19:06:49 UTC
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 20pulp-infra@redhat.com
2021-09-29 19:06:50 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Hello
bug set to VERIFIED as the HTB pulp related SELinux AVCs are fixed; two other unrelated AVCs found while testing and separated into new bugs
Bug 2012234 - SELinux: sshd denied read
Bug 2012250 - SELinux: denied name_connect comm="pulpcore-worker"
Thank you
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.10 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-2021:4702