Hide Forgot
Created attachment 1222799 [details] Ceilometer collector log Description of problem: When using Gnocchi as dispatcher for ceilometer meter datas, the collector fails to connect to Gnocchi Version-Release number of selected component (if applicable): OSP 9 openstack-tripleo-heat-templates-2.0.0-40.el7ost.noarch openstack-puppet-modules-8.1.8-3.el7ost.noarch openstack-ceilometer-collector-6.1.3-2.el7ost.noarch python-gnocchi-2.1.3-3.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Deploy overcloud with gnocchi as dispatcher (see additional info for config) 2. Run gnocchi metric list Actual results: No data in gnocchi $ source overcloudrc $ gnocchi metric list (empty) Expected results: Datas stored in gnocchi $ source overcloudrc $ gnocchi metric list +--------------------------------------+---------------------+----------------+--------------------------------------+ | id | archive_policy/name | name | resource_id | +--------------------------------------+---------------------+----------------+--------------------------------------+ | 296d2acd-024f-4935-8b93-0180a147a831 | low | image | e00be6f9-757b-40d3-94e0-f2d6c397fdac | | 8e15eb7d-5174-4cbb-88e9-dc9b7fab4242 | low | image.download | e00be6f9-757b-40d3-94e0-f2d6c397fdac | | 9120d45f-f818-4920-be3f-7a8f0b309bae | low | image.serve | e00be6f9-757b-40d3-94e0-f2d6c397fdac | | 9f5d06f0-952d-4f60-ba48-114251674f7a | low | image.size | e00be6f9-757b-40d3-94e0-f2d6c397fdac | Additional info: The following configuration is used : ----------------- parameter_defaults: CeilometerMeterDispatcher: 'gnocchi' ----------------- In attachment the python stack trace in ceilometer collector log. After restarting ceilometer collector in pacemaker, everything is working. # pcs resource restart openstack-ceilometer-collector-clone
I think this is expected in OSP 9, Gnocchi dispatcher was not configured by default in Ceilometer. Can you confirm Prad?
Closing as WONTFIX as this is not something we want to fix and it was a deliberate choice back then.
Sorry but that doesn't make any sense to me. You have the ability to choose your backend via CeilometerMeterDispatcher (database by default). https://github.com/openstack/tripleo-heat-templates/blob/stable/mitaka/overcloud.yaml#L40 But if you want to use gnocchi instead (which is supported in OSP9), it doesn't work out of the box but that's not something you want to fix ?
Dimitri, sorry, I may have misunderstood. Indeed if you set this option which allows "gnocchi" as a value and that is not apply, there might be something odd. I'll pass the ball to Prad which is more qualified than me on TripleO rules. :)
In OSP9, the way overcloud deployment runs is, all the services are deployed by puppet first and the keystone init runs in the end. Keystone init is whats responsible for creating the user and project in keystone. So when collector is deployed, gnocchi project/service is not in keystone yet and meter dispatcher initialization with gnocchi will fail. It gets added in the end as part of keystone init. Hence a restart of collector fixes the issue post deploy as at this point gnocchi user is in keystone and authentication passes. This is fixed in osp10 i believe where the keysont init is moved to puppet so it happens during the deployment, instead of in the end. Hence this wont happen in OSP10 or later. This is one of the reasons why we dont default to gnocchi as dispatcher in OSP9. I thought we documented this as a known thing somewhere in the docs.
Currently there is no documentation downstream about this issue. example 3 in https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/9/html-single/director_installation_and_usage/#sect-Configuring_Base_Parameters CeilometerMeterDispatcher in https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/9/html-single/director_installation_and_usage/#appe-Base_Parameters
Moving to 'NEW' to be triaged as resources allow.
LGTM, thanks.