Description of problem: ceilometer-nova service is not sending notifications due to being unconfigured. Taking http://docs.openstack.org/kilo/install-guide/install/yum/content/ceilometer-nova.html as a model and comparing it to a fresh install shows that the /etc/nova/nova.conf file lacks the notification_driver configuration, among others Version-Release number of selected component (if applicable): RHOS7/RHEL7.2 How reproducible: Run the tempest.api.telemetry.test_telemetry_notification_api.TelemetryNotificationAPITestJSON.test_check_nova_notificationer Actual results: Fails due to no notifications being recieved after 300 s Expected results: The test to pass Additional info:
Could please give more context? Which installer are you running? Which version? Thanks
This issue is also affecting RHOS7. After investigating, it seems that this is a packstack configuration problem. The configuration from ceilometer is nova.conf over compute nodes should follow the guide's details, i.e. [DEFAULT] ... instance_usage_audit = True instance_usage_audit_period = hour notify_on_state_change = vm_and_task_state notification_driver = messagingv2 However, after a default deployment, the following values for them can be found: [DEFAULT] notification_driver=ceilometer.compute.nova_notifier notification_driver=nova.openstack.common.notifier.rpc_notifier notification_driver= instance_usage_audit = False instance_usage_audit_period = month (This value doesn't really affect) notify_on_state_change = <None> After changing the values to the ones proposed in the configuration guide [1] and restarting the needed services, the nova notifications start working, and the test now passes. (.venv)[cloud-user@rhos7_rhel7 tempest-dir]$ python -m testtools.run tempest.api.telemetry.test_telemetry_notification_api.TelemetryNotificationAPITestJSON.test_check_nova_notification Tests running... Ran 1 test in 2.140s OK --- [1] http://docs.openstack.org/kilo/install-guide/install/yum/content/ceilometer-nova.html
Martin, OpenStack gerrit 253470 was merged, is there anything else left to fix this issue?
There is nothing else, I've submitted backports.