Red Hat Bugzilla – Bug 1033027
openlmi-hardware provider AVC denials
Last modified: 2016-07-19 06:37:15 EDT
Created attachment 827173 [details]
Relevant audit log parts
Description of problem:
SELinux prevents the OpenLMI HW provider from working.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install the HW provider scriptons:
easy_install --user openlmi-providers openlmi-providers-hardware
2. Run lmi -n hwinfo
ERROR: invocation failed for host "https://localhost": 'NoneType' object has no attribute 'ChassisPackageType'
There was 1 error:
(AttributeError) 'NoneType' object has no attribute 'ChassisPackageType
Pretty printed info about the host system.
BTW Pegasus should probably be an unconfined domain by default, since we have little idea of what people will do with it.
f93e231aa1c987dd1261d6e21ef7deee80a47490 adds a transition from pegasus_t to dmidecode_t to fix this issue in git.
Also added file name transition rules to make sure any content created via pegasus will get labeled correctly.
This is caused by openlmi-providers-hardware which should get own policy or pegasus_openlmi_unconfined_t. There is a RHEL7 bug where we are working on it.
Basically this is the same what we have for munin or nagios. So we don't to have unconfined_domain(pegasus) which could mask the fact that a policy is needed for a provider. We have pegasus_openlmi_unconfined_t domain for this.
Also I should write a blog about it.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.
More information and reason for this action is here:
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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
Thank you for reporting this bug and we are sorry it could not be fixed.