Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1623455

Summary: [starter] Prometheus instance on starter-us-west-1 is down
Product: OpenShift Container Platform Reporter: Stephen Cuppett <scuppett>
Component: MonitoringAssignee: Paul Gier <pgier>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.10.0CC: minden
Target Milestone: ---   
Target Release: 3.10.z   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
 Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-10 09:27:09 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 Stephen Cuppett 2018-08-29 12:16:32 UTC 
Description of problem:

https://redhat.service-now.com/surl.do?n=INC0777220

When attempting to connect to prometheus on starter-us-west-1 (https://prometheus-openshift-devops-monitor.a3c1.starter-us-west-1.openshiftapps.com/), we see "Application is not available".
 
Looking on the host we see that the prometheus pods are stuck in terminating state:
 
[user@host ~]$ oc get all -n openshift-devops-monitor
NAME READY STATUS RESTARTS AGE
pod/prometheus-0 1/5 Terminating 86 103d


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

3.10.14

Expected results:

Prometheus available
Comment 1 Paul Gier 2018-08-31 21:54:00 UTC 
For some reason the prometheus container was not properly shut down previously and was in a hung state.  It should be ok now.
Comment 2 Junqi Zhao 2018-09-03 06:20:51 UTC 
prometheus pod is running now
# oc get all -n openshift-devops-monitor
NAME                                 READY     STATUS    RESTARTS   AGE
pod/prometheus-0                     6/6       Running   0          2d

There is another Bug 1624697 filed
Comment 4 errata-xmlrpc 2019-01-10 09:27:09 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, 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/RHBA-2019:0026