Bug 794888 - /var/ctdb gets created with incorrect selinux context
Summary: /var/ctdb gets created with incorrect selinux context
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ctdb
Version: 6.3
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Sumit Bose
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-17 20:50 UTC by Justin Payne
Modified: 2012-06-20 14:15 UTC (History)
0 users

Fixed In Version: ctdb-1.0.114.3-4.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 14:15:20 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0904 0 normal SHIPPED_LIVE ctdb bug fix update 2012-06-19 20:46:57 UTC

Description Justin Payne 2012-02-17 20:50:28 UTC
Description of problem:

After running service ctdb start, the directory, files, and all subdirectories are created with incorrect selinux contexts.


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

ctdb-1.0.114.3-3.el6

How reproducible:

Always

Steps to Reproduce:
1. Install ctdb
2. Start the ctdb service
3. Check contexts with 'restorecon -Rnv /var/ctdb'
  
Actual results:

restorecon reset /var/ctdb context system_u:object_r:var_t:s0->system_u:object_r:ctdbd_var_lib_t:s0
restorecon reset /var/ctdb/locking.tdb.0 context unconfined_u:object_r:var_t:s0->unconfined_u:object_r:ctdbd_var_lib_t:s0
restorecon reset /var/ctdb/state context system_u:object_r:var_t:s0->system_u:object_r:ctdbd_var_lib_t:s0
restorecon reset /var/ctdb/state/persistent_health.tdb.0 context system_u:object_r:var_t:s0->system_u:object_r:ctdbd_var_lib_t:s0
restorecon reset /var/ctdb/state/recdb.tdb.0 context system_u:object_r:var_t:s0->system_u:object_r:ctdbd_var_lib_t:s0
restorecon reset /var/ctdb/state/vactune.tdb.0 context system_u:object_r:var_t:s0->system_u:object_r:ctdbd_var_lib_t:s0
restorecon reset /var/ctdb/persistent context system_u:object_r:var_t:s0->system_u:object_r:ctdbd_var_lib_t:s0
restorecon reset /var/ctdb/persistent/share_info.tdb.0 context unconfined_u:object_r:var_t:s0->unconfined_u:object_r:ctdbd_var_lib_t:s0
restorecon reset /var/ctdb/persistent/passdb.tdb.0 context unconfined_u:object_r:var_t:s0->unconfined_u:object_r:ctdbd_var_lib_t:s0
restorecon reset /var/ctdb/persistent/winbindd_idmap.tdb.0 context unconfined_u:object_r:var_t:s0->unconfined_u:object_r:ctdbd_var_lib_t:s0
restorecon reset /var/ctdb/persistent/account_policy.tdb.0 context unconfined_u:object_r:var_t:s0->unconfined_u:object_r:ctdbd_var_lib_t:s0
restorecon reset /var/ctdb/persistent/secrets.tdb.0 context system_u:object_r:var_t:s0->system_u:object_r:ctdbd_var_lib_t:s0
restorecon reset /var/ctdb/persistent/registry.tdb.0 context unconfined_u:object_r:var_t:s0->unconfined_u:object_r:ctdbd_var_lib_t:s0
restorecon reset /var/ctdb/connections.tdb.0 context unconfined_u:object_r:var_t:s0->unconfined_u:object_r:ctdbd_var_lib_t:s0
restorecon reset /var/ctdb/brlock.tdb.0 context unconfined_u:object_r:var_t:s0->unconfined_u:object_r:ctdbd_var_lib_t:s0
restorecon reset /var/ctdb/sessionid.tdb.0 context system_u:object_r:var_t:s0->system_u:object_r:ctdbd_var_lib_t:s0
restorecon reset /var/ctdb/g_lock.tdb.0 context unconfined_u:object_r:var_t:s0->unconfined_u:object_r:ctdbd_var_lib_t:s0
restorecon reset /var/ctdb/vactune.tdb.0 context system_u:object_r:var_t:s0->system_u:object_r:ctdbd_var_lib_t:s0

Expected results:

Selinux contexts created with correct values for ctdb operation.

Additional info:

Comment 4 Justin Payne 2012-03-01 16:35:23 UTC
Verified in ctdb-1.0.114.3-4.el6.x86_64

[root@dash-01 ~]# rpm -q ctdb
ctdb-1.0.114.3-4.el6.x86_64
[root@dash-01 ~]# restorecon -Rnv /var/ctdb
[root@dash-01 ~]#

Comment 5 errata-xmlrpc 2012-06-20 14:15:20 UTC
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-2012-0904.html


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