Bug 2059058 - LVMO should send alerts when VG utilization crosses certain limits
Summary: LVMO should send alerts when VG utilization crosses certain limits
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: lvm-operator
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ODF 4.10.0
Assignee: arun kumar mohan
QA Contact: Aviad Polak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-28 05:15 UTC by N Balachandran
Modified: 2023-08-09 16:46 UTC (History)
10 users (show)

Fixed In Version: 4.10.0-175
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-21 09:12:50 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage lvm-operator pull 103 0 None open Adding an alert mechanism into lvm-operator 2022-02-28 13:19:35 UTC
Github red-hat-storage lvm-operator pull 121 0 None open Bug 2059058: [release-4.10] Adding an alert mechanism into lvm-operator 2022-03-01 06:29:23 UTC

Description N Balachandran 2022-02-28 05:15:46 UTC 
Description of problem (please be detailed as possible and provide log
snippests):

The LVMO should send Alerts when the VG usage crosses a certain limit.

Version of all relevant components (if applicable):


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


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


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


Can this issue reproducible?


Can this issue reproduce from the UI?


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


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info:
Comment 4 Aviad Polak 2022-04-12 09:05:13 UTC 
looks good with 4.10-217
Note You need to log in before you can comment on or make changes to this bug.