glance-registry package drops incorrect logrotate config

Bug #1049314 reported by Justin Shepherd
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
glance (Ubuntu)
Fix Released
Medium
Unassigned
Precise
Fix Released
Undecided
Unassigned

Bug Description

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04 LTS"

Package: glance-registry (2012.1.3+stable~20120821-120fcf-0)

# cat /etc/logrotate.d/glance-registry
/var/log/glance/glance-api.log {
    daily
    missingok
    compress
    delaycompress
    notifempty
}

-----

The logrotate.d conf file points to the wrong log file (glance-api.log instead of glance-registry.log)

-----

The /etc/glance/glance-registry.conf file shipped with this package sets /var/log/glance/registry.log as the log file, where the logrotate.d conf file points to a different file than the default configuration setting:

http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/glance/precise-updates/view/head:/etc/glance-registry.conf#L16

Tags: canonistack

Related branches

description: updated
Revision history for this message
Justin Shepherd (jshepher) wrote :
Changed in glance (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Changed in glance (Ubuntu Precise):
status: New → Confirmed
Changed in glance (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package glance - 2012.2~rc1-0ubuntu1

---------------
glance (2012.2~rc1-0ubuntu1) quantal; urgency=low

  * New upstrem release.
  * debian/glance.logrotate: compress right logfiles when rotating them.
    (LP: #1049314)
 -- Chuck Short <email address hidden> Mon, 17 Sep 2012 07:44:11 -0500

Changed in glance (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Darren Birkett (darren-birkett) wrote :

is this going to be fixed in the essex packaging?

tags: added: canonistack
Changed in glance (Ubuntu Precise):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.