Comment 1 for bug 1663560

When deploying Fuel with built-in Ceilometer I cannot reproduce this bug, however I found that when using telemetry plugin, it does not override default value [1] for notification driver. This default value depends on ceilometer['enabled'] option [2], and in case of deployment with plugin ceilometer hash in hiera looks like:

root@node-1:~# hiera ceilometer
{"alarm_history_time_to_live"=>"604800",
 "event_time_to_live"=>"604800",
 "metering_time_to_live"=>"604800",
 "http_timeout"=>"600",
 "notification_driver"=>"<SERVICE DEFAULT>",
 "db_password"=>"fmXOxtcrzpMhOI67HE0vYku6",
 "enabled"=>"true",
 "metering_secret"=>"uWsXx80vnIs2ComsMVd8MgzU",
 "user_password"=>"lq95aSKTDdNllZPXS6ex0nTk"}

but initial value of enabled parameter in astute.yaml is:

ceilometer:
  db_password: fmXOxtcrzpMhOI67HE0vYku6
  enabled: false
  metering_secret: uWsXx80vnIs2ComsMVd8MgzU
  user_password: lq95aSKTDdNllZPXS6ex0nTk

As you can see notification driver is SERVICE DEFAULT, because its value had been caculated before "enabled" parameter was overriden by plugin's hiera.pp manifest. This means after deployment notification_driver will be abcent in config. In order to fix this I recommend to set notification_driver explicitly to "messaging" in plugin's hiera manifest [1]. So for me it looks like bug is invalid for MOS. It should be fixed in plugin.

[1] https://github.com/openstack/fuel-plugin-openstack-telemetry/blob/master/deployment_scripts/puppet/manifests/hiera.pp#L16

[2] https://github.com/openstack/fuel-library/blob/master/deployment/puppet/osnailyfacter/manifests/globals/globals.pp#L470