Bug 980592 - SELinux is preventing /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/bin/java from 'write' accesses on the directory publish.
SELinux is preventing /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/bin...
Status: CLOSED ERRATA
Product: Fedora
Classification: Fedora
Component: freeipa (Show other bugs)
19
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Rob Crittenden
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-02 15:41 EDT by Dean Hunter
Modified: 2013-07-08 09:19 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-07-08 09:19:37 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Dean Hunter 2013-07-02 15:41:05 EDT
Description of problem:

An SELinux alert is being raised during ipa-server-install: 

SELinux is preventing /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/jre/bin/java from 'write' accesses on the directory publish. 

I am using selinux-policy from updates-testing to resolve bug #976159.


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

freeipa-server-3.2.1-1.fc19.x86_64
selinux-policy-3.12.1-57.fc19.x86_64


How reproducible: Consistent


Steps to Reproduce:
1. Build a new Fedora 19 VM
2. yum update --assumeyes
3. yum update --assumeyes --enablerepo updates-testing selinux-policy
4. yum install --assumeyes bind bind-dyndb-ldap freeipa-server
5. ipa-server-install ....


Actual results:

The server appears to install successfully, but there is an SELinux alert.


Expected results:

Successful server install without any alerts


Additional info:

I have reported bug #980588 on selinux-policy.  I need to understand the impact of this alert on the IPA server.
Comment 1 Dean Hunter 2013-07-08 09:19:37 EDT
The problem is resolved with selinux-policy-3.12.1-59.fc19.noarch.

Note You need to log in before you can comment on or make changes to this bug.