v10.1.18: RackspaceMonitoringValidationError - alarmParseError - Failed to parse alarm about rpc-maas HOT 10 CLOSED

I'm willing to bet that the alarm criteria wasn't properly templated but it's too late right now for me to look into this.

@mancdaz @hughsaunders can you look at this tomorrow?

from rpc-maas.

@byronmccollum It looks like you're missing some new vars, can you ensure the following are set:

The problem is that in Juno we don't default vars (because the use of defaults/main.yml only really came into play in the kilo restructure). Unfortunately that means there is a manual process in Juno, that we haven't done a good job of documenting at this point.

rabbitmq_queued_messages_excluding_notifications_threshold: 100
rabbitmq_queue_growth_rate_threshold: 15

from rpc-maas.

If that doesn't resolve the problem let me know and I'll check it out!

from rpc-maas.

That was it. Thanks.

from rpc-maas.

@asettle @robb-romans can you think of a good way we can document this? The issue is essentially:

In juno, when we add new vars there is no way to automatically copy them, so during upgrades we need to copy over new vars (in etc/rpc_deploy/user_variables.yml) for some monitors (the above 2 in particular for this example) - otherwise the vars aren't specified. This is only an issue for Juno, and more specifically only for juno upgrades.

from rpc-maas.

more specifically only for juno upgrades.

To be clear, juno -> juno upgrades (e.g., 10.1.17 -> 10.1.18)

from rpc-maas.

@andymcc - no problem. We can just add a note in the current upgrade guide and in the release notes. Clarifying that this is just for Juno and not relevant for the Kilo upgrades?

from rpc-maas.

Change that, just the v10 release notes should be fine. See here: http://docs.rackspace.com/rpc/api/v10/bk-rpc-v10-releasenotes/content/rpc-upgrade.html

from rpc-maas.

also: https://github.com/rpcdocs/rpcdocs/issues/449

from rpc-maas.

This repo is no longer actively maintained. If this issue is still valid please open a new issue at https://github.com/rcbops/rpc-openstack/issues

from rpc-maas.