Ceilometer collector cannot reconnect to rabbitmq after RabbitMQ failover
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Fix Released
|
High
|
MOS Ceilometer | ||
5.1.x |
In Progress
|
High
|
MOS Ceilometer | ||
6.1.x |
Fix Released
|
High
|
MOS Maintenance |
Bug Description
VERSION:
feature_groups:
- mirantis
production: "docker"
release: "6.0"
api: "1.0"
build_number: "58"
build_id: "2014-12-
astute_sha: "16b252d93be6aa
fuellib_sha: "fde8ba5e11a1ac
ostf_sha: "a9afb68710d809
nailgun_sha: "5f91157daa6798
fuelmain_sha: "81d38d6f2903b5
oslo.messaging version:
at 6.0 env:
root@node-2:~# apt-cache policy python-
python-
Installed: 1.4.1-fuel6.
at 6.1 env (Verizon):
python-
Steps to reproduce:
1. Deploy cluster with the following parameters:
3 controllers+mongo, KVM, 5 GB RAM
1 compute+ceph, Supermicro, 16 GB RAM
Sahara, Ceilometer enabled, Ceph for volumes, Ceph for images, Ceph for ephemeral volumes
2. Disable rabbitmq:
pcs resource disable master_
wait while master and slaves was stopped
3. Enable rabbitmq:
pcs resource enable master_
wait while master and slaves was started
Expected result:
Ceilometer collector successfully reconnected to rabbitmq
Actual result:
On all controller nodes in /var/log/
2015-10-28 11:43:01.113 14829 INFO oslo.messaging.
2015-10-28 11:43:02.115 14829 INFO oslo.messaging.
2015-10-28 11:43:02.123 14829 ERROR oslo.messaging.
2015-10-28 11:43:32.154 14829 INFO oslo.messaging.
2015-10-28 11:43:33.155 14829 INFO oslo.messaging.
2015-10-28 11:43:33.170 14829 ERROR oslo.messaging.
Metering queue in rabbit is not empty:
root@node-1:~# rabbitmqctl list_queues | grep metering
metering.sample 224
q-metering-plugin 0
q-metering-
q-metering-
q-metering-
q-metering-
q-metering-
q-metering-
After ~10 minutes collector on one controller reconnects to rabbitmq, but collectors on other two controllers don't.
For example, all ceilometer-
Workaround: restart ceilometer-
Changed in mos: | |
assignee: | nobody → MOS Ceilometer (mos-ceilometer) |
tags: | added: ceilometer customer-found |
Changed in mos: | |
importance: | Undecided → High |
description: | updated |
no longer affects: | oslo.messaging |
Changed in mos: | |
milestone: | 6.0-updates → 6.0-mu-7 |
Changed in mos: | |
status: | Confirmed → Fix Committed |
tags: | added: support |
tags: | added: on-verification |
tags: | removed: on-verification |
This might be a known issue with oslo.messaging in 6.0.
Why file it if we have maintenance updates for 6.0 that fix the bug?