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

Bug 916622

Summary: Default object-server.conf doesn't contain a object-expirer config section
Product: Red Hat OpenStack Reporter: Derek Higgins <derekh>
Component: openstack-swiftAssignee: Pete Zaitcev <zaitcev>
Status: CLOSED ERRATA QA Contact: Martina Kollarova <mkollaro>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 2.1CC: derekh, ncredi, zaitcev
Target Milestone: snapshot5Keywords: Triaged
Target Release: 2.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-swift-1.7.4-11.el6ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-04 18:00:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Candidate 1
none
Candidate 3 apevec: review+, derekh: review+

Description Derek Higgins 2013-02-28 14:05:09 UTC 
[root@ps2 ~]# service openstack-swift-object-expirer start
Starting swift-object-expirer:                             [  OK  ]
[root@ps2 ~]# service openstack-swift-object-expirer status
object-expirer dead but pid file exists
[root@ps2 ~]# cat /var/log/swift-startup.log 
Unable to find object-expirer config section in /etc/swift/object-server.conf
[root@ps2 ~]# 
[root@ps2 ~]# rpm -qa | grep -i swift-obj
openstack-swift-object-1.7.4-7.el6ost.noarch
Comment 2 Pete Zaitcev 2013-03-01 19:39:16 UTC 
Created attachment 704293 [details]
Candidate 1

How about this - let the start to introspect. Note that this patch does not add /etc/swift/object-expirer.conf. Should we?
Comment 3 Derek Higgins 2013-03-04 09:33:17 UTC 
(In reply to comment #2)
> Created attachment 704293 [details]
> Candidate 1
> 
> How about this - let the start to introspect. Note that this patch does not
> add /etc/swift/object-expirer.conf. Should we?

Yup, I think we should, would adding the section to the proxy config file and using it simply be enough? or create a new expirer config file. wouldn't including either of these in the package remove the need to introsect ?
Comment 4 Pete Zaitcev 2013-03-05 02:00:24 UTC 
Adding a section [object-expirer] to the proxy-server.conf is sufficient,
but it still requires almost exactly the same patch as Candidate 1, because
the name of the config is different from "object-server.conf" that the
common function swift_action() insists on using in such case.
Comment 5 Pete Zaitcev 2013-03-05 05:31:27 UTC 
Created attachment 705288 [details]
Candidate 2

ok, how about now?
Comment 9 Pete Zaitcev 2013-03-06 19:01:33 UTC 
Created attachment 706212 [details]
Candidate 3

Not sure if you guys appreciate this peacemeal approach, but this seems to
work in my testing. This includes verifying that expirer works by itself.
Comment 10 Derek Higgins 2013-03-07 13:08:28 UTC 
Comment on attachment 706212 [details]
Candidate 3

looks good to me
Comment 12 errata-xmlrpc 2013-04-04 18:00:33 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0706.html