Bug 2088359

Summary:	Send VG Metrics even if storage is being consumed from thinPool alone
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Leela Venkaiah Gangavarapu <lgangava>
Component:	lvm-operator	Assignee:	N Balachandran <nibalach>
Status:	CLOSED ERRATA	QA Contact:	Aviad Polak <apolak>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.11	CC:	jolmomar, lgangava, muagarwa, nberry, ocs-bugs, odf-bz-bot, sapillai
Target Milestone:	---
Target Release:	ODF 4.11.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	4.11.0-81	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-24 13:53:39 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 Leela Venkaiah Gangavarapu 2022-05-19 09:50:04 UTC

Description of problem (please be detailed as possible and provide log
snippests):
- when every device-class targets only thinpool we'll never send the metrics of volume group
- admin may find it difficult to get Volume Group metrics in above scenario


Version of all relevant components (if applicable):
- odf-lvmo-4.10


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
na

Is there any workaround available to the best of your knowledge?
No

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
1

Can this issue reproducible?
yes

Can this issue reproduce from the UI?
no

If this is a regression, please provide more details to justify this:
no

Steps to Reproduce:
1. Create an ODF LVMO 4.11 Setup
2. Observe the absence of Volume Group metrics


Actual results:
- No VG metrics but only thinpool metrics are available

Expected results:
- VG metrics should be available

Additional info:

Comment 8 errata-xmlrpc 2022-08-24 13:53:39 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 (Important: Red Hat OpenShift Data Foundation 4.11.0 security, enhancement, & bugfix update), 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/RHSA-2022:6156