openstack/openstack-ansible
Code Issues Proposed changes

Change maas_notification_plan to npManaged

Browse Source 
When set to npTechnicalContactEmail for customers without a cloud
account, alarm creation will fail with an "Unable to create Alarm due to issues with account contact information. Please contact support"
error. Changing to npManaged allows alert creation to complete so alarm
tickets can be created.

Issue rcbops/ansible-lxc-rpc#402
This commit is contained in:
Christopher H. Laco 2014-10-27 13:07:15 -04:00
parent 046bdd32ca
commit 47f992328c
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
etc/rpc_deploy/user_variables.yml
View File

@ -92,7 +92,7 @@ maas_username: "{{ rackspace_cloud_username }}"
maas_api_key: "{{ rackspace_cloud_api_key }}"
maas_auth_token: some_token
maas_api_url: https://monitoring.api.rackspacecloud.com/v1.0/{{ rackspace_cloud_tenant_id }}
maas_notification_plan: npTechnicalContactsEmail
maas_notification_plan: npManaged
# By default we will create an agent token for each entity, however if you'd
# prefer to use the same agent token for all entities then specify it here
#maas_agent_token: some_token

2
scripts/cloudserver-aio.sh
View File

@ -206,7 +206,7 @@ maas_username: "{{ rackspace_cloud_username }}"
maas_api_key: "{{ rackspace_cloud_api_key }}"
maas_auth_token: some_token
maas_api_url: https://monitoring.api.rackspacecloud.com/v1.0/{{ rackspace_cloud_tenant_id }}
maas_notification_plan: npTechnicalContactsEmail
maas_notification_plan: npManaged
# By default we will create an agent token for each entity, however if you'd
# prefer to use the same agent token for all entities then specify it here
#maas_agent_token: some_token