Red Hat Bugzilla – Bug 246795
SELinux is preventing /usr/sbin/lvm (lvm_t) "write" to .cache (lvm_etc_t).
Last modified: 2012-10-16 04:13:34 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:126.96.36.199) Gecko/20070515 Firefox/188.8.131.52
Description of problem:
SELinux denied access requested by /usr/sbin/lvm. It is not expected that this access is required by /usr/sbin/lvm and this access may signal an intrusion attempt. It is also possible that the specific version or configuration of the application is causing it to require additional access.Allowing AccessSometimes labeling problems can cause SELinux denials. You could try to restore the default system file context for .cache, restorecon -v .cache If this does not work, there is currently no automatic way to allow this access. Instead, you can generate a local policy module to allow this access - see FAQ Or you can disable SELinux protection altogether. Disabling SELinux protection is not recommended. Please file a bug report against this package.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.System --> Administration --> Logical Volume Management
selinux troubleshooter displays alert
This is running CentOS 5 kernel, CentOS release 5 (Final)
restorecon -R -v /etc/lvm should fix the problem. You can get the update u1
I believe a permanant fix for this is coming from LVM.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Could you try the new policy available at the link below and reply
whether the new packages solve your problem. Thank you.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.