Bug 1476456 - colllectd ipmi does not start with selinux deny
colllectd ipmi does not start with selinux deny
Status: NEW
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted (Show other bugs)
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Lukas Vrabec
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2017-07-29 03:48 EDT by Daniel Rowe
Modified: 2018-05-03 04:32 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Daniel Rowe 2017-07-29 03:48:59 EDT
Description of problem:

Collectd IPMI pluging does not work out of the box and get a deny:

type=AVC msg=audit(1501313729.643:373): avc:  denied  { read write } for  pid=6620 comm="ipmi" name="ipmi0" dev="devtmpfs" ino=1287 scontext=system_u:system_r:collectd_t:s0 tcontext=system_u:object_r:ipmi_device_t:s0 tclass=chr_file permissive=0

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

collectd-ipmi.x86_64                                                                                5.7.2-5.fc26

How reproducible:


Steps to Reproduce:
1. Box with IPMI like a Dell Server
2. Install collectd and the IPMI plugin
3. Start collect and get deny

Actual results:

selinux deny

Expected results:

Works out of the box
Comment 1 Daniel Rowe 2017-07-29 03:59:07 EDT
This is what is needed.

#============= collectd_t ==============

#!!!! This avc is allowed in the current policy
allow collectd_t ipmi_device_t:chr_file { ioctl open read write };
Comment 2 Fedora End Of Life 2018-05-03 04:32:01 EDT
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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.

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