Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1553476

Summary:	The ended_at field is not being updated in gnocchi when volumes are deleted
Product:	Red Hat OpenStack	Reporter:	nalmond
Component:	openstack-ceilometer	Assignee:	Mehdi ABAAKOUK <mabaakou>
Status:	CLOSED ERRATA	QA Contact:	Sasha Smolyak <ssmolyak>
Severity:	high	Docs Contact:
Priority:	medium
Version:	10.0 (Newton)	CC:	alsilva, apannu, eglynn, jruzicka, jthomas, mabaakou, pkilambi, srevivo
Target Milestone:	z8	Keywords:	Triaged, ZStream
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-ceilometer-7.1.1-7.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-17 15:32:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description nalmond 2018-03-08 22:59:54 UTC

Description of problem:
After enabling the ceilometer meters for cinder volumes, the data appears, but after the volume is deleted, the ended_at time is not updated.

Version-Release number of selected component (if applicable):


How reproducible:
Consistently in customer environment and lab (both osp 10)

Steps to Reproduce:
1. enable volume metrics with volume.* in pipeline.yaml
2. create a volume
3. delete the volume
4. run 'openstack metric resource show <volume-id>'

Actual results:

| ended_at              | None                                                |

Expected results:

ended_at reflects the date/time the volume was deleted

Additional info:
This does work in RHOSP 11. Gnocchi is looking for the volume.delete.start event, can we backport this to RHOSP 10?

I can provide access to the lab if needed.

Comment 16 errata-xmlrpc 2018-05-17 15:32:27 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:1594