Comment 2 for bug 1518338

This is may be at least in part the result of the openstack-bad-id to internal-gnocchi-uuid mapping that is done[1]. If I recall correctly at least some of the hardware ids are not uuids.

So what will happen is that resource list will list a bunch of opaque ids that appear to bear no relation to the external ids. However if you were to make a query using the external resource id you'd probably get the expected thing.

I'm away from any way of being able to test or demonstrate this but I reckon there's a way easily show what is going on with a gnocchiclient example.

Because of the mapping shim and the bad external ids, this is just going to happen. The way to work around it is to be aware of the external ids and use them in queries, not enumerate resources ids in gnocchi to find the expected id. This isn't ideal but is a tax we pay for inconsistent ids.

[1] https://review.openstack.org/#/c/216390/