Ceilometer (master) amulet test failing on expected notifier relation data.
00:22:13.845 DEBUG:runner:2017-08-15 18:46:11,500 test_210_ceilometer_agent_nova_compute_relation DEBUG: Checking ceilometer:nova-compute relation data...
#### actual relation data:
00:22:39.113 DEBUG:runner:2017-08-15 18:46:36,772 _validate_dict_data DEBUG: actual: {u'subordinate_configuration': u'{"nova": {"/etc/nova/nova.conf": {"sections": {"DEFAULT": [["instance_usage_audit", "True"], ["instance_usage_audit_period", "hour"], ["notify_on_state_change", "vm_and_task_state"]]}}}}', u'private-address': u'172.17.110.15'}
#### expected relation data:
00:22:39.113 DEBUG:runner:2017-08-15 18:46:36,773 _validate_dict_data DEBUG: expected: {'subordinate_configuration': '{"nova": {"/etc/nova/nova.conf": {"sections": {"DEFAULT": [["instance_usage_audit", "True"], ["instance_usage_audit_period", "hour"], ["notify_on_state_change", "vm_and_task_state"], ["notification_driver", "ceilometer.compute.nova_notifier"], ["notification_driver", "nova.openstack.common.notifier.rpc_notifier"]]}}}}', 'private-address': <bound method OpenStackAmuletUtils.valid_ip of <charmhelpers.contrib.openstack.amulet.utils.OpenStackAmuletUtils object at 0x7f6f219de890>>}
00:22:39.113 DEBUG:runner:unexpected relation data in ceilometer-service - subordinate_configuration:{"nova": {"/etc/nova/nova.conf": {"sections": {"DEFAULT": [["instance_usage_audit", "True"], ["instance_usage_audit_period", "hour"], ["notify_on_state_change", "vm_and_task_state"]]}}}}
00:22:39.552 DEBUG:runner:Exit Code: 1
This is likely part of the telemetry refresh work, and if the new behavior is intended, we should update the test.
Or as previously discussed, it may be ok to remove the 1 test altogether as its value could be considered low compared to its brittleness.