ceilometermiddleware should read oslo configs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ceilometermiddleware |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Description:
The ceilometer integration with swift connects with rabbitmq using the transport URL given in the [filter:ceilometer] section in the swift-proxy.conf config file. For most OpenStack projects, the connection parameters are additionally configured in an [oslo_messaging_*] section of the config file. However, ceilometermiddl
http://
Impact:
The rabbit driver in oslo.messaging uses separate SSL configs that cannot be provided in the transport URL and are instead, in general, provided in that [oslo_messaging
Steps to reproduce:
1. Configure rabbitmq to use ssl and enable ssl_listeners on port 5671. Set verify to verify_peer and fail_if_
2. Change the [filter:
3. Add the section in swift-proxy.conf (I've also tried adding it in swift.conf and ceilometer.conf): [oslo_messaging
Expected behavior:
Swift operates normally and can make a successful connection to rabbitmq.
Actual behavior:
The swift-proxy server starts but contains errors in the logs:
AMQP server 192.168.
Rabbitmq logs confirm that this isn't an issue with the password:
=ERROR REPORT==== 17-Mar-
Error on AMQP connection <0.3416.0>:
{ssl_upgrade_
Command line operations on objects and containers never finish.
It's possible I'm just missing a configuration step and misplacing the config, in which case this could just be a documentation bug :)
I can confirm this issue is still present in current master. We attempted to to set [oslo_messaging _rabbit] ssl but it has no effect.