Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
The libstoragemgmt package comes from EPEL, but the daemon is already confined in RHEL-7.
Version-Release number of selected component (if applicable):
libstoragemgmt-0.0.22-1.el6.i686
libstoragemgmt-ibm-v7k-plugin-0.0.22-1.el6.noarch
libstoragemgmt-netapp-plugin-0.0.22-1.el6.noarch
libstoragemgmt-nstor-plugin-0.0.22-1.el6.noarch
libstoragemgmt-python-0.0.22-1.el6.noarch
libstoragemgmt-smis-plugin-0.0.22-1.el6.noarch
libstoragemgmt-targetd-plugin-0.0.22-1.el6.noarch
selinux-policy-3.7.19-213.el6.noarch
selinux-policy-doc-3.7.19-213.el6.noarch
selinux-policy-minimum-3.7.19-213.el6.noarch
selinux-policy-mls-3.7.19-213.el6.noarch
selinux-policy-targeted-3.7.19-213.el6.noarch
How reproducible:
always
Steps to Reproduce:
# run_init service libstoragemgmtd status
Authenticating root.
Password:
lsmd is stopped
# run_init service libstoragemgmtd start
Authenticating root.
Password:
Starting lsmd daemon: [ OK ]
# run_init service libstoragemgmtd status
Authenticating root.
Password:
lsmd (pid 5154) is running...
# ps -efZ | grep lsmd
system_u:system_r:initrc_t:s0 456 5154 1 0 14:20 ? 00:00:00 /usr/bin/lsmd
unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 root 5170 3019 0 14:20 pts/0 00:00:00 grep lsmd
#
Actual results:
* lsmd runs as initrc_t
Expected results:
* lsmd runs in its own SELinux domain
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2014-1568.html