Comment 6 for bug 1664898

The ceilometer-agent-central still exists but it runs /usr/bin/ceilometer-polling
The service is still called ceilometer-agent-central and has a systemd init file.

This change attempted to address this issue:
https://github.com/openstack/charm-ceilometer/commit/3816946e2f769c37ca2ed15aa6a49e9583ad8900
https://bugs.launchpad.net/charms/+source/ceilometer/+bug/1606787

However it is failing on a simple Mitaka HA deploy:
http://pastebin.ubuntu.com/24009855/
http://pastebin.ubuntu.com/24009878/

And it also fails during charm upgrade as in comment #3

< wolsen> right, but I see what happened
< wolsen> afaict, the systemd init file was provided for ceilometer-agent-central and pointed at the ceilometer-polling
< wolsen> so you could use the same service

< thedac> Interesting. So does that make the PR unnecessary?
< wolsen> hmm I'm not sure its necessary no

It seems it is at least to some degree. I tested with the above commit reverted and this also fails with:
couldn't find command: ceilometer-agent-central

This was not discovered earlier because the amulet tests do not run HA tests. And the service ceilometer-agent-central is not stopped 100% of the time. The juju status can look good but crm status shows breakage.

So we need to address 3 issues.
1) Determine if the rename is necessary (res_ceilometer_agent_central->res_ceilometer_polling). If so possibly change the required services.

2) Fix the hand off to hacluster to correctly monitor the ceilometer-polling regardless of what it is called. This could be a disparity between the service name "ceilometer_agent_central" and the command that needs to be run: /usr/bin/ceilometer-polling.

3) Handle upgrades of the charm when the previous version uses the old resource. This needs to include removal of previously setup res_ceilometer_agent_central resources.