Bug 1149757 - remove libvirt logrotate configuration from vdsm
Summary: remove libvirt logrotate configuration from vdsm
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: General
Version: 4.17.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-3.6.0-rc
: 4.17.2
Assignee: Yaniv Bronhaim
QA Contact: Lukas Svaty
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-06 14:41 UTC by Yaniv Bronhaim
Modified: 2016-02-10 19:11 UTC (History)
12 users (show)

Fixed In Version: ovirt-3.6.0-alpha1.2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-22 13:31:07 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-3.6.0+
ylavi: planning_ack+
rule-engine: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 33925 0 master MERGED tool: Remove leftover libvirtd.log rotating logic. Never

Description Yaniv Bronhaim 2014-10-06 14:41:03 UTC 
Description of problem:
vdsm stops to set libvirt log configuration since ovirt-3.5 , therefore we should remove also the libvirt logrotate config
Comment 1 Sven Kieske 2015-07-27 15:24:56 UTC 
is this documented in user documentation?

it should be done, because the old behaviour was different and users might expect
that it still works the same way if the relase notes do not mention it (just a link to this BZ is probably not enough, because there are too many of them).
Comment 2 Red Hat Bugzilla Rules Engine 2015-10-18 08:33:38 UTC 
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.
Comment 3 Lukas Svaty 2015-12-10 13:14:01 UTC 
verified in vdsm-4.17.13-1.el7ev.noarch
Comment 4 Sandro Bonazzola 2015-12-22 13:31:07 UTC 
oVirt 3.6.0 has been released and the bz verified, moving to closed current release.
Note You need to log in before you can comment on or make changes to this bug.