Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 2131031

Summary: SELinux is preventing java from create access on the directory .pki
Product: Red Hat Enterprise Linux 8 Reporter: Sonam <sshewale>
Component: pki-servlet-engineAssignee: Coty Sutherland <csutherl>
Status: CLOSED MIGRATED QA Contact: idm-cs-qe-bugs
Severity: medium Docs Contact:
Priority: unspecified    
Version: ---CC: ehelms, jalbrech, lzap, peter.vreman, rhcs-maint
Target Milestone: rcKeywords: MigratedToJIRA, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-06 11:13:21 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 Sonam 2022-09-29 18:04:34 UTC
Description of problem:

SELinux AVC during installation on tomcat user /usr/share/tomcat/.pki directory. The Installation finishes successfully and also after the installation the directory /usr/share/tomcat/.pki. does also not exists

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

Satellite 6.11.2


How reproducible: The alert is reproducible when the installer is re-run:


Steps to Reproduce:

1. Re-run the below command to reproduce the issue:
   # satellite-installer --verbose --verbose-log-level=info


Actual results: Every time the satellite installer is run an SELinux violation is reported 


Expected results: No SELinux violation


Additional info:


$ sudo grep sealert /var/log/messages | grep -v 'Activating service'
Sep 16 07:21:01 li-lc-2750 setroubleshoot[103614]: SELinux is preventing /usr/lib/jvm/java-11-openjdk-11.0.16.1.1-1.el8_6.x86_64/bin/java from create access on the directory /usr/share/tomcat/.pki. For complete SELinux messages run: sealert -l 79f06cd8-7742-46e6-8384-12d2ca6c26d4
Sep 16 07:38:18 li-lc-2750 setroubleshoot[3926]: SELinux is preventing /usr/lib/jvm/java-11-openjdk-11.0.16.1.1-1.el8_6.x86_64/bin/java from create access on the directory .pki. For complete SELinux messages run: sealert -l 79f06cd8-7742-46e6-8384-12d2ca6c26d4

type=AVC msg=audit(09/16/2022 07:20:54.762:590700) : avc:  denied  { create } for  pid=103466 comm=java name=.pki scontext=system_u:system_r:tomcat_t:s0 tcontext=system_u:object_r:usr_t:s0 tclass=dir permissive=0

Comment 2 Josh Albrecht 2023-08-31 16:25:05 UTC
In the previous BZ investigation for this issue (https://bugzilla.redhat.com/show_bug.cgi?id=2051851) the Candlepin conclusion was that tomcat itself is creating the directory under it's own home directory (/usr/share/tomcat) and allowing this actions is not up to Candlepin, but tomcat. This being the case, I will change the component to tomcat.

Comment 4 RHEL Program Management 2023-09-06 11:10:00 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 5 RHEL Program Management 2023-09-06 11:13:21 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 "RHEL-" 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.