Bug 1117686 - Package requires further selinux flag to be set
Summary: Package requires further selinux flag to be set
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: mod_cluster
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Marek Goldmann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-09 08:15 UTC by Juraci Paixão Kröhling
Modified: 2015-06-29 21:31 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 21:31:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
selinux alert file, as seen in troubleshooter (2.36 KB, text/plain)
2014-07-09 08:15 UTC, Juraci Paixão Kröhling
no flags Details

Description Juraci Paixão Kröhling 2014-07-09 08:15:45 UTC
Created attachment 916670 [details]
selinux alert file, as seen in troubleshooter

Description of problem:
The package mod_cluster for Fedora 20 is not working "out of the box", generating a selinux alert upon starting of httpd. 

The selinux message is: "SELinux is preventing /usr/sbin/httpd from name_bind access on the udp_socket ."

The recommended action to take is, with 89.3 confidence: "setsebool -P nis_enabled 1" (more details on the attached alert file).

Version-Release number of selected component (if applicable):
Latest from Fedora 20 at the time of writing (1.2.6-1.fc20)

How reproducible:
Always

Steps to Reproduce:
1. yum install mod_cluster -y
2. comment out proxy_balancer_module from /etc/conf.modules.d/00-proxy.conf
3. uncomment all lines on /etc/conf.d/mod_cluster.conf (except the first "real" comment lines)
4. systemctl start httpd

Actual results:
Server starts, but alert is shown, probably preventing mod_cluster from properly working

Expected results:
No alerts in an out of the box installation. If mod_cluster requires this flag to properly work, it should do it upon installation. 

Additional info:

Comment 1 Fedora End Of Life 2015-05-29 12:19:55 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-06-29 21:31:55 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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