Red Hat Bugzilla – Bug 469162
Directory /var/lib/iscsi is NOT owned by iscsi-initiator-utils
Last modified: 2010-04-21 08:49:50 EDT
Description of problem:
The package owns /var/lock/iscsi but does not own /var/lib/iscsi. Why?
The filesystem on newly installed RHEL-5.3 machine contains /var/lib/iscsi with wrong SELinux label (correct context is recorded in SELinux policy but is not applied in the filesystem until you call restorecon -v /var/lib/iscsi).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
* install new RHEL-5.3 machine (via RHTS)
* install iscsi-initiator-utils package
# rpm -qf /var/lock/iscsi
# rpm -qf /var/lib/iscsi
file /var/lib/iscsi is not owned by any package
# matchpathcon -V /var/lock/iscsi
# matchpathcon -V /var/lib/iscsi
/var/lib/iscsi has context root:object_r:rpm_var_lib_t:s0, should be system_u:object_r:iscsi_var_lib_t:s0
Is this due to a goof up in the spec?
Is there also supposed to be a
I think that both /var/lock/iscsi and /var/lib/iscsi should be written in %files section.
Adding devel ACK. This seems like it is low risk so I am also setting the 5.3 flag (not sure if I need to set the exception flag too).
(In reply to comment #3)
> (not sure if I need to set the exception flag too).
Yes, after beta ships the BZ has to have exception or blocker. Otherwise it gets deflagged. I'll set blocker, since we really should not ship it this way.
Checked in iscsi-initiator-utils 220.127.116.118-0.12.el5.
verified in snapshot 6.
Installed: iscsi-initiator-utils.i386 0:18.104.22.1688-0.17.el5
[root@localhost ~]# rpm -qf /var/lock/iscsi
[root@localhost ~]# rpm -qf /var/lib/iscsi
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 therefore 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.