Bug 949686 - vdsm.log ownership is root:root when log rotate run at the same time as supervdsm writes to the same log file
Summary: vdsm.log ownership is root:root when log rotate run at the same time as super...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.2.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: 3.1.4
Assignee: Yaniv Bronhaim
QA Contact: Elad
URL:
Whiteboard: infra
Depends On: 912308
Blocks: 891843 917401
TreeView+ depends on / blocked
 
Reported: 2013-04-08 18:52 UTC by Idith Tal-Kohen
Modified: 2016-02-10 19:25 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
When the vdsm.log file is removed, either manually or by logrotate, the supervdsm user can create the log file and set its ownership to root:root. When this happens, the vdsmd service is stopped until the user resets the vdsm.log ownership to vdsm:kvm, and restarts the service. This update separates supervdsm log to a supervdsm.log file, so after vdsm.log is rotated it remains owned by vdsm:kvm.
Clone Of: 912308
Environment:
Last Closed: 2013-05-01 18:25:15 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 376713 0 None None None Never
Red Hat Product Errata RHBA-2013:0774 0 normal SHIPPED_LIVE rhev 3.1.4 - vdsm bug fix update 2013-05-01 22:23:56 UTC
oVirt gerrit 12940 0 None None None Never

Comment 3 Elad 2013-04-29 15:04:37 UTC 
Checked on RHEVM - 3.1 - SI28.1

vdsm-4.10.2-1.13.el6ev.x86_64


After rotate of vdsm.log during writing of supervdsm, the log file ownership remains vdsm kvm
Comment 5 errata-xmlrpc 2013-05-01 18:25:15 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-2013-0774.html
Note You need to log in before you can comment on or make changes to this bug.