Bug 1507048

Summary:	open-vm-tools logfiles lacks correct labels
Product:	Red Hat Enterprise Linux 7	Reporter:	Beat Rubischon <brubisch>
Component:	selinux-policy	Assignee:	Lukas Vrabec <lvrabec>
Status:	CLOSED ERRATA	QA Contact:	Milos Malik <mmalik>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.4	CC:	lvrabec, mgrepl, mmalik, plautrba, ssekidde, zpytela
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	selinux-policy-3.13.1-185.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-10 12:44:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1122832

Description Beat Rubischon 2017-10-27 14:11:02 UTC

Description of problem:

open-vm-tools are creating two logfiles:
/var/log/vmware-vmsvc.log
/var/log/vmware-vgauthsvc.log.0

Both files are created with the label system_u:object_r:var_log_t:s0, a restorecon relables it to system_u:object_r:vmware_log_t:s0

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

selinux-policy-3.13.1-166.el7_4.4.noarch

How reproducible:

always

Steps to Reproduce:
1. Provision RHEL 7 & open-vm-tools
2. restorecon -Rnv /var/log

Actual results:

restorecon reset /var/log/vmware-vmsvc.log context system_u:object_r:var_log_t:s0->system_u:object_r:vmware_log_t:s0
restorecon reset /var/log/vmware-vgauthsvc.log.0 context system_u:object_r:var_log_t:s0->system_u:object_r:vmware_log_t:s0

Expected results:

No relabling necessairy as logfiles are created correctly.

Additional info:

Comment 2 Lukas Vrabec 2017-10-30 11:03:41 UTC

Hi, 

Could you run daemons: vmstoolsd and vgauthd

and then attach output of: 

# ps -efZ 

Thanks,
Lukas.

Comment 12 errata-xmlrpc 2018-04-10 12:44:59 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.

https://access.redhat.com/errata/RHBA-2018:0763