Bug 2260340

Summary: CephMonLowNumber alert is raised only when metrics exporter pod is restarted
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Joy John Pinto <jopinto>
Component: ceph-monitoringAssignee: umanga <uchapaga>
Status: CLOSED ERRATA QA Contact: jpinto
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.15CC: ebenahar, muagarwa, nladha, odf-bz-bot, uchapaga
Target Milestone: ---   
Target Release: ODF 4.15.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.15.0-130 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-03-19 15:32:21 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:
Bug Depends On: 2168042, 2259852    
Bug Blocks:    

Description Joy John Pinto 2024-01-25 13:17:02 UTC
Description of problem (please be detailed as possible and provide log
snippests):
CephMonLowNumber alert is raised only when metrics exporter pod is restarted 

On a vmware cluster where more than five failure domains are added, CephMonLowNumberalert is not shown automatically, metrics exporter pod needs to be restarted to get alerts

Version of all relevant components (if applicable):
OCP 4.15 and ODF 4.15.0-122

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?
Restart metrics pod to get alerts
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?
Yes

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

Steps to Reproduce:
1.Install a 3master 6 worker node cluster
2.Label the worker nodes in different failure domains using command "oc label node compute-2 failure-domain.beta.kubernetes.io/zone=rack-2 --overwrite=true"
3. Wait for the "CephMonLowNumber" alert to be raised 


Actual results:
Alert is raised only if metrics pod is restarted

Expected results:
Whenever failure domain count reaches above 5, alert should be raised automatically

Additional info:

Comment 7 Joy John Pinto 2024-02-07 06:18:08 UTC
Verified with OCP 4.15.0-0.nightly-2024-02-05-224816 and ODF 4.15.0-134, If the cluster has five or more than five failure domains automatically CephMonLowNumber alert is raised and we are able to update Ceph Mon count to five through the configure modal. hence closing the bug as verified

Comment 9 errata-xmlrpc 2024-03-19 15:32:21 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.15.0 security, enhancement, & bug fix 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-2024:1383