Closed xeregin closed 9 years ago
Looks like we'll need to grab https://github.com/rcbops/rpc-openstack/commit/42bd085e798548239c48b769709f2c24ada64b0a and https://github.com/rcbops/rpc-openstack/commit/c3950819cda7951429414e897d734d6759276af1 to account for this.
@xeregin I see you're testing 10.1.9; does this need to go in 10.1.10?
This was also reported on https://bugs.launchpad.net/openstack-ansible/+bug/1466171, so it's existed for a couple versions.
Double checked - this was a result of mistakes in tagging. The change is merged (https://github.com/rcbops/rpc-maas/pull/209), and will go into 10.1.10.
@BjoernT @b3rnard0
I was testing 10.1.9. Missed that bug in launchpad.
rabbitmq_status.py (10.1.9) does not provide the 'rabbitmq_max_channels_per_conn--' metric, which causes the MaaS checks (installed from os-ansible-deployment/rpc_deployment/playbooks/monitoring/) to alert.
As a sample, here is the output from a recent call to this script:
rabbitmq_status.py from this repo needs to be modified to support this required metric.
Cheers! :)