Bug 2006342 - CephMdsMissingReplicas alert is not propagated into PagerDuty
Summary: CephMdsMissingReplicas alert is not propagated into PagerDuty
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: odf-managed-service
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Dhruv Bindra
QA Contact: Elena Bondarenko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-21 14:02 UTC by Filip Balák
Modified: 2022-06-08 12:17 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-16 19:49:56 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift ocs-osd-deployer pull 94 0 None open AlertRelabelConfigSecret added to apply namespace label to alerts 2021-10-04 10:27:03 UTC

Description Filip Balák 2021-09-21 14:02:27 UTC
Description of problem:
When one of rook-ceph-mds-ocs-storagecluster-cephfilesystem deployments doesn't have replica, the alert CephMdsMissingReplicas is not shown in PagerDuty.

Version-Release number of selected component (if applicable):
ocs-operator.v4.8.1
ocs-osd-deployer-qe.v1.1.0

How reproducible:
2/2

Steps to Reproduce:
1. Scale down deployment rook-ceph-mds-ocs-storagecluster-cephfilesystem-a to 0
2. Check alerts in PagerDuty

Actual results:
The alert is not propagated. In internal prometheus it is visible but not in PagerDuty.

Expected results:
The alert should be propagated to PagerDuty when using ODF Managed Service addon.

Additional info:
To access internal prometheus locally, the port must be forwarded:
 $ oc port-forward svc/prometheus-operated 9090 -n openshift-storage

Comment 1 Elena Bondarenko 2021-12-14 15:37:52 UTC
Filip ran all pagerduty tests with 
ocs-operator.v4.8.5
ocs-osd-deployer-qe.v1.1.2
ocp 4.9.9

Alerts are working correctly


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