/etc/logrotate.d/ceph and /etc/logrotate.d/ceph-base both manage /var/log/ceph/ which causes "error: ceph-base:1 duplicate log entry for /var/log/ceph/ceph-mon.[hostname].log" during hourly logrotate

Bug #1635844 reported by Karl-Philipp Richter
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ceph (Ubuntu)
Fix Released
Medium
James Page
Yakkety
Fix Released
Medium
Unassigned

Bug Description

[Impact]
Multiple log rotate configs attempt to manage the same set of log files

[Test Case]
apt install ceph-mon ceph-osd (xenial)
upgrade to yakkety
<error message below will be seen>

[Regression Potential]
Minimal - logrotate configuration will be correctly removed on upgrades from the ceph package (although its now in the ceph-common, not ceph-base package with the proposed update to cover radosgw as well)

[Original Bug Report]
/etc/logrotate.d/ceph and /etc/logrotate.d/ceph-base both manage /var/log/ceph/ which causes "error: ceph-base:1 duplicate log entry for /var/log/ceph/ceph-mon.[hostname].log" during hourly logrotate

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ceph 10.2.3-0ubuntu2
Uname: Linux 4.8.0-040800-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Sat Oct 22 16:32:23 2016
InstallationDate: Installed on 2015-04-20 (550 days ago)
InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2)
ProcEnviron:
 TERM=screen.xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: ceph
UpgradeStatus: Upgraded to yakkety on 2016-10-19 (2 days ago)

Revision history for this message
Karl-Philipp Richter (krichter722) wrote :
Revision history for this message
James Page (james-page) wrote :

I suspect this is a problem with upgrades from pre-yakkety versions of ceph, not purging the old logrotate configuration file from the ceph package.

Changed in ceph (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
James Page (james-page)
Changed in ceph (Ubuntu):
status: Triaged → Fix Committed
James Page (james-page)
Changed in ceph (Ubuntu):
assignee: nobody → James Page (james-page)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ceph - 10.2.5-0ubuntu2

---------------
ceph (10.2.5-0ubuntu2) zesty; urgency=medium

  * d/rules: Install upstream provided systemd targets and ensure they
    are enabled and started on install to ensure that integrations aligned
    to upstream packaging work with Ubuntu packages (LP: #1646583).
  * d/rules,d/p/powerpc_libatomic.patch: Ensure linking with -latomic,
    resolving FTBFS on powerpc architecture.

 -- James Page <email address hidden> Tue, 17 Jan 2017 11:10:40 +0000

Changed in ceph (Ubuntu):
status: Fix Committed → Fix Released
James Page (james-page)
description: updated
description: updated
Changed in ceph (Ubuntu Yakkety):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello Karl-Philipp, or anyone else affected,

Accepted ceph into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ceph/10.2.5-0ubuntu0.16.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in ceph (Ubuntu Yakkety):
status: Triaged → Fix Committed
tags: added: verification-needed
Revision history for this message
James Page (james-page) wrote :

Upgraded to proposed packages, only ceph-common logrotate configuration installed post upgrade.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ceph - 10.2.5-0ubuntu0.16.10.1

---------------
ceph (10.2.5-0ubuntu0.16.10.1) yakkety; urgency=medium

  * New upstream stable release (LP: #1649856):
    - d/p/32bit-ftbfs.patch: Drop, no longer required.
    - d/p/*: Refresh.
    - d/ceph-common.install: Switch to RSA keys for drop.ceph.com.
  * d/rules: Install upstream provided systemd targets and ensure they
    are enabled and started on install to ensure that integrations aligned
    to upstream packaging work with Ubuntu packages (LP: #1646583).
  * d/ceph.{postinst,preinst,postrm}: Ensure that ceph logrotate
    configuration is purged on upgrade from pre-yakkety installs
    (LP: #1635844).
  * d/ceph-base.*,d/*.logrotate: Install logrotate configuration
    in ceph-common, ensuring that all daemons get log rotation on
    log files, deal with removal of logrotate configuration in
    ceph-base for upgrades (LP: #1609866).

 -- James Page <email address hidden> Wed, 18 Jan 2017 11:39:04 +0000

Changed in ceph (Ubuntu Yakkety):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Update Released

The verification of the Stable Release Update for ceph has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

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.