Bug 1553476 - The ended_at field is not being updated in gnocchi when volumes are deleted
Summary: The ended_at field is not being updated in gnocchi when volumes are deleted
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ceilometer
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: z8
: 10.0 (Newton)
Assignee: Mehdi ABAAKOUK
QA Contact: Sasha Smolyak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-08 22:59 UTC by nalmond
Modified: 2022-08-16 11:01 UTC (History)
8 users (show)

Fixed In Version: openstack-ceilometer-7.1.1-7.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-17 15:32:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-4935 0 None None None 2022-08-16 11:01:34 UTC
Red Hat Product Errata RHBA-2018:1594 0 None None None 2018-05-17 15:32:30 UTC

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


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