telemetry plugin runs ceilometer-dbsync

[Dmitry Sutyagin]

Reproduced on MOS 9.2 + telemetry plugin 1.0 (downloaded from https://www.mirantis.com/software/fuel-plugins/)

During deployment puppet runs "ceilometer-dbsync" which does not make sense when telemetry plugin is used, because ceilometer.conf has incorrect mongodb connect line (no IP) and also mongo servers are not deployed at all. This task fails by timeout in 15min, failure is ignored.

Does not affect deployment except increasing deployment time.

Extract from puppet.log:

2017-02-27 19:57:59 +0000 /Stage[main]/Ceilometer::Logging/Ceilometer_config[DEFAULT/syslog_log_facility]/ensure (notice): created
2017-02-27 20:13:56 +0000 /Stage[main]/Ceilometer::Db::Sync/Exec[ceilometer-dbsync]/returns (notice): Option "verbose" from group "DEFAULT" is deprecated for removal. Its value may be silently ignored in the future.
2017-02-27 20:13:56 +0000 /Stage[main]/Ceilometer::Db::Sync/Exec[ceilometer-dbsync]/returns (notice): Option "os_endpoint_type" from group "service_credentials" is deprecated. Use option "interface" from group "service_credentials".
2017-02-27 20:13:56 +0000 /Stage[main]/Ceilometer::Db::Sync/Exec[ceilometer-dbsync]/returns (notice): Option "username" from group "service_credentials" is deprecated. Use option "user-name" from group "service_credentials".
2017-02-27 20:13:56 +0000 /Stage[main]/Ceilometer::Db::Sync/Exec[ceilometer-dbsync] (err): Failed to call refresh: ceilometer-dbsync --config-file=/etc/ceilometer/ceilometer.conf returned 1 instead of one of [0]
2017-02-27 20:13:56 +0000 /Stage[main]/Ceilometer::Db::Sync/Exec[ceilometer-dbsync] (err): ceilometer-dbsync --config-file=/etc/ceilometer/ceilometer.conf returned 1 instead of one of [0]

As you can see, it took 15 min to get past this task.

[Dmitry Sutyagin (dsutyagin)]

This task - https://github.com/openstack/fuel-plugin-openstack-telemetry/blob/master/deployment_tasks.yaml#L96 should somehow skip running ceilometer-dbsync. Not sure yet how this could be implemented.

[Oleksiy Molchanov (omolchanov)]

We cannot skip whole task, because it is configuring a lot of stuff except dbsync. Also there is no possibility to skip dbsync without refactoring of granular tasks. I am marking this as won't fix, because actually it doesn't break deployment.