Telemetry group catalog_type is metering but should be telemetry

Bug #1359375 reported by David Kranz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ceilometer
Won't Fix
Undecided
Unassigned
tempest
Invalid
Low
Unassigned

Bug Description

devstack also sets the sql catalog issue to metering which should also be telemetry

Revision history for this message
David Kranz (david-kranz) wrote :

I'm not sure what ordering is required between changing devstack and tempest is required to fix this.

Revision history for this message
Matthew Treinish (treinish) wrote :

So you're going to have a fun chicken and egg problem here. Devstack doesn't set catalog_types for any of the services in the tempest config. So when you change how devstack registers the service in the keystone catalog it will fail tempest, because it can't find the service. But, if you go to change the default value in tempest it will fail because the catalog doesn't contain a telemetry service type.

I think the only way out of this is to push the devstack patch so that is also sets the tempest config option. We can then change the value in tempest and remove the default override in devstack.

Changed in tempest:
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Ghanshyam Mann (ghanshyammann) wrote :

As telemetry tests moved to plugin, transferring this bug to telemetry from tempest

- https://github.com/openstack/ceilometer/blob/master/ceilometer/tests/tempest/config.py

Changed in tempest:
status: Triaged → Invalid
Revision history for this message
gordon chung (chungg) wrote :

tbh, this doesn't seem worth the trouble.

Changed in ceilometer:
status: New → Won't Fix
Sean Dague (sdague)
no longer affects: devstack
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.