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 2172833

Summary:	SELinux errors in journal during content-export
Product:	Red Hat Satellite	Reporter:	Vladimír Sedmík <vsedmik>
Component:	Pulp	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.13.0	CC:	dalley, egolov, ehelms, rlavi
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, Triaged, WorkAround
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	pulpcore-selinux-2.0.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 16:08:52 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 Vladimír Sedmík 2023-02-23 09:17:58 UTC

Description of problem:
When performing a content export, the export succeeds but SELinux denial errors are logged in journal.


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


How reproducible:
always


Steps to Reproduce:
1. Have a Satellite with some content synced.
2. Run content export (no matter the type nor format)
# hammer content-export complete repository --format importable --organization-id 1 --id 2


Actual results:
Errors like following seen in journal:
Feb 23 04:06:05 satellite.redhat.com /SetroubleshootPrivileged.py[37552]: failed to retrieve rpm info for /var/lib/selinux/targeted/active/modules/400/pulpcore
Feb 23 04:06:09 satellite.redhat.com setroubleshoot[37536]: SELinux is preventing /usr/bin/python3.9 from write access on the directory Export-<product_name>. For complete SELinux messages run: sealert -l fb7d5ec5-a1b6-4cef-855c-1232d8dc0533


Expected results:
No such errors in journal.


Additional info:
Setting fcontext to pulpcore_var_lib_t for the particular directory resolves the issue:
# semanage fcontext -a -t pulpcore_var_lib_t /var/lib/pulp/exports/Default_Organization/Export-<product_name>
# restorecon -v /var/lib/pulp/exports/Default_Organization/Export-<product_name>

Comment 1 Eric Helms 2023-08-03 12:58:43 UTC

As this was reported a while back on a snap, is this still an issue being seen on 6.13 GA or 6.14 development builds?

Comment 2 Vladimír Sedmík 2023-08-04 11:58:05 UTC

Yes, the issue has been just reproduced on 6.14.0 snap 10 and 6.13.3 snap 2:

Aug 04 07:55:45 satellite.redhat.com /SetroubleshootPrivileged.py[11396]: failed to retrieve rpm info for /var/lib/selinux/targeted/active/modules/400/pulpcore
Aug 04 07:55:47 satellite.redhat.com setroubleshoot[11368]: SELinux is preventing /usr/bin/python3.9 from write access on the directory labeled var_lib_t. For complete SELinux messages run: sealert -l 66186877-c5c6-455f-ad29-6c58aee48b31

Comment 3 Evgeni Golov 2023-08-10 13:01:05 UTC

@Pulp Team:
/var/lib/pulp/export is something that Katello/Satellite defines as a default export path (https://github.com/theforeman/puppet-foreman_proxy_content/blob/96258dd5e8a36e9f94e6ba7d3a04bcbfbfd7a57c/manifests/init.pp#L238)
However, we think now that Pulp2 is dead-dead-dead, https://github.com/pulp/pulpcore-selinux/blob/main/pulpcore.fc#L18-L24 can be simplified to something like
/var/lib/pulp(/.*)?	gen_context(system_u:object_r:pulpcore_var_lib_t,s0)
/var/lib/pulp/pulpcore_static(/.*)? 	gen_context(system_u:object_r:httpd_sys_content_t,s0)

Comment 4 Evgeni Golov 2023-08-10 13:02:13 UTC

Ewoud opened a nice PR for that change: https://github.com/pulp/pulpcore-selinux/pull/69

Comment 5 Eric Helms 2024-06-06 16:08:52 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.