Bug 1257838 - Ceilometer keeps deleted data
Summary: Ceilometer keeps deleted data
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ceilometer
Version: 6.0 (Juno)
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: ---
: 8.0 (Liberty)
Assignee: Eoghan Glynn
QA Contact: Yurii Prokulevych
URL:
Whiteboard:
Depends On:
Blocks: 1378914
TreeView+ depends on / blocked
 
Reported: 2015-08-28 08:29 UTC by Ondrej
Modified: 2019-09-12 08:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1378914 (view as bug list)
Environment:
Last Closed: 2016-09-23 13:50:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
customer screenshot (298.76 KB, image/png)
2015-08-28 08:29 UTC, Ondrej
no flags Details

Description Ondrej 2015-08-28 08:29:45 UTC
Created attachment 1067927 [details]
customer screenshot

Description of problem:
after deleting a tenant, horizon dashboard overview displays the deleted tenant by the id.

keystone tenant-delete $tenant



Version-Release number of selected component (if applicable):
openstack-ceilometer-collector-2014.2.3-5.el7ost.noarch
python-ceilometerclient-1.0.12-1.el7ost.noarch
openstack-ceilometer-notification-2014.2.3-5.el7ost.noarch
openstack-ceilometer-alarm-2014.2.3-5.el7ost.noarch
openstack-ceilometer-common-2014.2.3-5.el7ost.noarch
openstack-ceilometer-central-2014.2.3-5.el7ost.noarch
openstack-ceilometer-api-2014.2.3-5.el7ost.noarch
python-ceilometer-2014.2.3-5.el7ost.noarch

How reproducible:
always

Steps to Reproduce:
1.create project(tenant)
2.launch instance
3.delete project(with running instance / with terminated instance)

Actual results:
data still stored

Expected results:
data deleted

Additional info:

Comment 4 Julien Danjou 2016-09-23 13:50:50 UTC
So this is not possible in the Ceilometer API where you cannot delete anything. We don't plan on improving this API anyway.

But the good news is that it's actually implemented in Gnocchi which is shipped with OSP 9 and by default enabled in OSP 10.


Note You need to log in before you can comment on or make changes to this bug.