Bug 2071976 - PagerDuty alerting is not working
Summary: PagerDuty alerting is not working
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-managed-service
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Ohad
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-05 10:36 UTC by Filip Balák
Modified: 2023-08-09 17:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-28 06:49:06 UTC
Embargoed:


Attachments (Terms of Use)

Description Filip Balák 2022-04-05 10:36:33 UTC
Description of problem:
Tested on Provider cluster with QE addon. There is also missing smtp secret.

Version-Release number of selected component (if applicable):
mcg-operator.v4.10.0
ocs-operator.v4.10.0
ocs-osd-deployer.v2.0.0
odf-operator.v4.10.0
ose-prometheus-operator.4.8.0
OCP 4.9.25

How reproducible:
1/1

Steps to Reproduce:
1. Set PagerDuty integration into ocs-provider-qe-deadmanssnitch
2. Shut down one osd
3. Wait for alerts

or try port forward:
oc port-forward svc/prometheus-operated 9090 -n openshift-storage
and visit http://localhost:9090/alerts

Actual results:
Alerting is not working and list of alerts in http://localhost:9090/alerts is empty

Expected results:
Alerting is working

Additional info:
$ oc get secrets -n openshift-storage | grep ocs-provider-qe
addon-ocs-provider-qe-parameters                            Opaque                                2      165m
ocs-provider-qe-deadmanssnitch                              Opaque                                1      165m
ocs-provider-qe-pagerduty                                   Opaque                                1      165m

Comment 2 Filip Balák 2022-04-06 12:29:26 UTC
This was fixed with https://bugzilla.redhat.com/show_bug.cgi?id=2071923 --> VERIFIED


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