Swift object expirer upstart job missing

Bug #1235495 reported by William Kelly on 2013-10-04
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu Cloud Archive
swift (Ubuntu)
James Page
James Page

Bug Description

The swift object expirer service is required to use the object expiration feature in swift. Currently, there is no upstart job to manage this service.

I encountered this bug on the grizzly packages in cloud archive (1.8.x) and verified that it persists on the latest saucy packages.

Here's a simple job that works:

root@spc-will-9753-admin1:/etc/init.d# cat /etc/init/swift-object-expirer.conf
# swift-object-expirer - SWIFT Object Expirer
# The swift object expirer.
# Shamelessly copied from swift-object.conf by Marc Cluet
description "SWIFT Object Expirer"
author "Will Kelly <email address hidden>"

start on runlevel [2345]
stop on runlevel [016]

pre-start script
  if [ -f "/etc/swift/object-expirer.conf" ]; then
    exec /usr/bin/swift-init object-expirer start
    exit 1
end script

post-stop exec /usr/bin/swift-init object-expirer stop


Related branches

Changed in swift (Ubuntu):
importance: Undecided → Medium
no longer affects: swift
James Page (james-page) on 2013-12-09
Changed in swift (Ubuntu):
status: New → Triaged
Changed in cloud-archive:
status: New → Triaged
importance: Undecided → High
James Page (james-page) wrote :

Hi Will

I was going to put this in the swift-object package, but reading the docs in a bit more detail, this feels like something that needs to be in its own package as it does not run on object storage nodes - probably alongside the proxy server:


How does this sound? I've proposed a merge for the icehouse packages on this basis.

James Page (james-page) on 2014-02-24
Changed in swift (Ubuntu):
assignee: nobody → James Page (james-page)
Changed in swift (Ubuntu Trusty):
status: Triaged → In Progress
Ron Pedde (ron-pedde) wrote :

I think a separate package makes sense -- it's very possible this is run on an internal management box, and not part of the cluster proper. Making it a separate package lets people run it wherever it makes sense in their environment.

I think this is a good idea.

Yes, I believe a separate package is the right decision.

James Page (james-page) on 2014-02-25
Changed in swift (Ubuntu Trusty):
status: In Progress → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package swift - 1.13.0-0ubuntu1

swift (1.13.0-0ubuntu1) trusty; urgency=medium

  [ Chuck Short ]
  * New upstream release.

  [ James Page ]
  * Add object-expirer package and associated configuration (LP: #1235495):
    - d/control: Add swift-object-expirer package, break/replace swift-object
      from earlier versions.
    - d/swift-object.install: Drop install of swift-object-expirer.
    - d/swift-object-expirer.{install,upstart}: Install swift-object-expirer
      and associated upstart configuration.
    - d/rules,object-expirer.conf: Provide basic object-expirer configuration.
    - debian/swift-object-expirer.docs: Add full example configuration to docs.
  * d/rules,swift-container.swift-container-sync.upstart: Add upstart
    configuration for swift-container-sync process (LP: #1250171).
 -- Chuck Short <email address hidden> Thu, 06 Mar 2014 12:29:10 -0500

Changed in swift (Ubuntu Trusty):
status: Fix Committed → Fix Released
Chuck Short (zulcss) on 2014-04-02
Changed in cloud-archive:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers