tripleo::profile::base::ceilometer::collector always does a db sync

[Alex Schultz]

While writing tests for tripleo::profile::base::ceilometer::collector I discovered that we are always include ceilometer::db::sync in step 4+ for any node despite only wanting to do it on the bootstrap node in the tripleo profile.

The problem is that we expect this logic to be followed:
https://github.com/openstack/puppet-tripleo/blob/master/manifests/profile/base/ceilometer/collector.pp#L62-L64

But in ceilometer::db, ceilometer::db::sync is included by default so it gets included anytime ceilometer::db is included in the catalog. This means we do ceilometer::db::sync on the bootstrap node in step 3 and all nodes with this profile for step 4+

https://github.com/openstack/puppet-ceilometer/blob/master/manifests/db.pp#L56

[Alex Schultz (alex-schultz)]

https://review.openstack.org/380414

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/puppet-tripleo 6.0.0 release.