Bug 1698533

Summary: olm-operator metrics failing to scrape
Product: OpenShift Container Platform Reporter: Frederic Branczyk <fbranczy>
Component: OLMAssignee: Evan Cordell <ecordell>
Status: CLOSED DUPLICATE QA Contact: Jian Zhang <jiazha>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.1.0   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-12 02:36:17 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 Frederic Branczyk 2019-04-10 14:26:17 UTC 
Description of problem:

The monitoring targets configured in Prometheus are not successfully being scraped. This is causing alerts to fire and olm-operator metrics not being collected.

```
openshift-operator-lifecycle-manager/olm-operator/0 (0/1 up) 
Get https://10.128.0.10:8081/metrics: dial tcp 10.128.0.10:8081: connect: connection refused
```

Version-Release number of selected component (if applicable):

4.1

How reproducible:

Always

Steps to Reproduce:
1.
2.
3.

Actual results:

All olm-operator targets are unsucessfully scraped.

Expected results:

All olm-operator targets are sucessfully scraped.

Additional info:
Comment 1 Jian Zhang 2019-04-12 02:36:17 UTC 
Hi, Frederic

Thanks for your report! Bug 1689836 is tracing this issue.
I'd like to close this one as a duplicate.

*** This bug has been marked as a duplicate of bug 1689836 ***