RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1331513 - Aodh 2.0.0-1 release does not include the default Mitaka configuration file
Summary: Aodh 2.0.0-1 release does not include the default Mitaka configuration file
Keywords:
Status: CLOSED EOL
Alias: None
Product: RDO
Classification: Community
Component: openstack-ceilometer
Version: trunk
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: Kilo
Assignee: Eoghan Glynn
QA Contact: Yurii Prokulevych
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-28 17:23 UTC by Peter Nordquist
Modified: 2016-05-19 16:10 UTC (History)
5 users (show)

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


Attachments (Terms of Use)

Description Peter Nordquist 2016-04-28 17:23:22 UTC
Description of problem:
The current release of the openstack-aodh-common in the Mitaka release repository still has the same configuration file from the Liberty release.  As far as I can tell this is because the configuration file was imported into the package repository statically.  See https://github.com/openstack-packages/aodh/blob/mitaka-rdo/aodh.conf.sample.  Can this be changed to act like the Ceilometer spec file and generate the configuration when the rpm is built?

Comment 2 Chandan Kumar 2016-05-19 15:40:33 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.

Comment 3 Peter Nordquist 2016-05-19 15:56:40 UTC
Your version selector for RDO does not have Mitaka in it.  Is Mitaka End of Life?  Plus I can't update the target release field, somehow it set it to Kilo when I switched from Red Hat OpenStack to RDO.

Comment 4 Chandan Kumar 2016-05-19 16:10: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.