The Ussuri+ pollster.d/polling.yaml error message mentioned in #6 and #7 appears to be a red herring. I have implemented functional tests [0] which look at which metrics get published by the ceilometer-agent-compute. I have run these tests various times against all releases between Rocky and Wallaby. For all these releases, changing the charm config option `enable-all-pollsters` has an impact on the polling.yaml file, which in turn has an impact on the published metrics. This proves that the ceilometer-agent-compute **can** find this file. So the ceilometer-agent-compute not finding this file can't be the root cause of the original bug.
The Ussuri+ pollster. d/polling. yaml error message mentioned in #6 and #7 appears to be a red herring. I have implemented functional tests [0] which look at which metrics get published by the ceilometer- agent-compute. I have run these tests various times against all releases between Rocky and Wallaby. For all these releases, changing the charm config option `enable- all-pollsters` has an impact on the polling.yaml file, which in turn has an impact on the published metrics. This proves that the ceilometer- agent-compute **can** find this file. So the ceilometer- agent-compute not finding this file can't be the root cause of the original bug.
[0] https:/ /github. com/openstack- charmers/ zaza-openstack- tests/pull/ 615