Bug 1314465 - openstack-aodh-expirer does not looks like a regular service
Summary: openstack-aodh-expirer does not looks like a regular service
Keywords:
Status: CLOSED EOL
Alias: None
Product: RDO
Classification: Community
Component: openstack-ceilometer
Version: trunk
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: Kilo
Assignee: Amit Ugol
QA Contact: Yurii Prokulevych
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-03 16:54 UTC by Attila Fazekas
Modified: 2016-05-19 15:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-19 15:31:27 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Attila Fazekas 2016-03-03 16:54:10 UTC 
Description of problem:

openstack-aodh-expirer is packaged separately as it would be a service,
however aodh-expirer exits immediately after it did the clenaup. 

aodh-expirer should be in the same package as aodh-dbsync.

It should be called from cron job, like cinder db purge, or the keystone token flush  (when the tokens are stored in the db).

openstack-aodh-expirer-2.0.0.0b3-0.20160301155358.27fb5f7.fc23.noarch
Comment 1 Chandan Kumar 2016-05-19 15:31:27 UTC 
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.
Note You need to log in before you can comment on or make changes to this bug.