Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1080790

Summary: Remove usages of vdsm logging conf from vdsm-tool
Product: [Retired] oVirt Reporter: Yaniv Bronhaim <ybronhei>
Component: vdsmAssignee: Dima Kuznetsov <dkuznets>
Status: CLOSED CURRENTRELEASE QA Contact: Gil Klein <gklein>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.5CC: alonbl, amuller, bazulay, bugs, danken, dkuznets, dougsland, gklein, iheim, mgoldboi, oourfali, rbalakri, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-12 14:17:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Yaniv Bronhaim 2014-03-26 07:30:20 UTC 
Description of problem:

vdsm-tool usually runs with root privileges (as admin tool). if a verb can access or uses vdsm logging config file it can lead to ownership changes on vdsm log files.

We need to separate all usages of logging between vdsm logging config to vdsm-tool logging.

currently the only use-case relevant for this case is in too/upgrade.py. this should be fixed and the hack of changing the ownership on pre-task (http://gerrit.ovirt.org/#/c/25912/) should be remove.

shouldn't be any correlation between vdsm.logging.conf to vdsm-tool.


Actual results:
vdsm.log ownership becomes root:root
Comment 1 Alon Bar-Lev 2014-03-26 10:59:22 UTC 
command-line tools should not log into /var/log

command-line tools should have optional log parameter for these who want to log.
Comment 2 Douglas Schilling Landgraf 2014-03-29 14:27:05 UTC 
*** Bug 1080580 has been marked as a duplicate of this bug. ***
Comment 3 Gil Klein 2014-10-12 14:17:42 UTC 
This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA