Bug 1475006

Summary:	Gnocchi fails to create manila.share.size metric
Product:	Red Hat OpenStack	Reporter:	Victoria Martinez de la Cruz <vimartin>
Component:	openstack-ceilometer	Assignee:	Victoria Martinez de la Cruz <vimartin>
Status:	CLOSED ERRATA	QA Contact:	Sasha Smolyak <ssmolyak>
Severity:	low	Docs Contact:
Priority:	low
Version:	12.0 (Pike)	CC:	jruzicka, mabaakou, pkilambi, srevivo
Target Milestone:	ga	Keywords:	Triaged
Target Release:	12.0 (Pike)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-ceilometer-9.0.2-0.20170925173740.1057885.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-13 21:44:48 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 Victoria Martinez de la Cruz 2017-07-25 20:22:29 UTC

Description of problem:

availability_zone and name parameters were marked as required for the manila share resource-type while these are not always needed by manila. This makes the creation of the manila.share.size metric file and hence the displayed data is not accurate.


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


How reproducible: In a deployment with manila (notifications enabled) and ceilometer with gnocchi configured as the backend, create a new manila share.


Steps to Reproduce:
1. Create a manila share
2. Check the metric list

Actual results: The metric cannot be created due to missing required attributes.

Expected results: Gnocchi should collect manila.share.size metrics when receiving manila.create.*, manila.delete.*, manila.shrink.* and manila.extend.* events and show them on the metric list.


Additional info:

Comment 6 Sasha Smolyak 2017-12-13 11:58:04 UTC

The attributes are there, nothing is missing anymore.
Verified.
The code is there

Comment 9 errata-xmlrpc 2017-12-13 21:44:48 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/RHEA-2017:3462