RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1282746 - Swift's proxy-server is not configured to use ceilometer
Summary: Swift's proxy-server is not configured to use ceilometer
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: RDO
Classification: Community
Component: openstack-packstack
Version: trunk
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: trunk
Assignee: Javier Peña
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks: 1296899
TreeView+ depends on / blocked
 
Reported: 2015-11-17 10:17 UTC by Daniel Mellado
Modified: 2017-06-18 13:45 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
: 1296899 (view as bug list)
Environment:
Last Closed: 2017-06-18 13:45:49 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 316147 0 None None None 2016-05-18 16:04:50 UTC

Description Daniel Mellado 2015-11-17 10:17:04 UTC
Description of problem:

The /etc/swift/proxy-server.conf generated by the installer doesn't take into consideration the object storage service for telemetry, thus there's no ceilometer support for swift.

After configuring it manually as the install guide states (http://docs.openstack.org/icehouse/install-guide/install/yum/content/ceilometer-install-swift.html) it refuses to start   


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Install packstack
2. Run tempest.scenario.test_object_storage_telemetry_middleware.TestObjectStorageTelemetry
3. It'll fail due to swift nor configured to use ceilometer

Actual results:

Swift is not producing notifications using ceilometer. Manual attemps to fix it break swift-proxy. This is making tempest.scenario.test_object_storage_telemetry_middleware.TestObjectStorageTelemetry fail

Expected results:

To get ceilometer notifications from swift and the test passing.

Additional info:

Comment 3 Javier Peña 2016-05-18 16:04:51 UTC
https://review.openstack.org/316147 includes a proposed change that fixes this.

Comment 4 Christopher Brown 2017-06-18 13:45:49 UTC
Change was merged.


Note You need to log in before you can comment on or make changes to this bug.