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

Bug 1614907

Summary: [admin] should be able to create prometheus services via OLM
Product: OpenShift Container Platform Reporter: Evan Cordell <ecordell>
Component: MonitoringAssignee: Evan Cordell <ecordell>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.11.0CC: jiazha
Target Milestone: ---   
Target Release: 3.11.0   
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: 2018-10-11 07:24:38 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 Evan Cordell 2018-08-10 17:03:18 UTC 
Description of problem:
Prometheus pods don't start via the Prometheus operator installed from OLM.

Version-Release number of selected component (if applicable): 
ansible 2.6 and openshift-ansible master branch.
oc v3.11.0-0.9.0
olm image:  quay.io/coreos/olm@sha256:44b445850b3e612c062424c3727bb85048ec8e71407b39985786d29aa20f5c79
catalog image: 
quay.io/coreos/catalog@sha256:20886d49205aa8d8fd53f1c85fad6a501775226da25ef14f51258b7066e91064
prometheus operator image:
quay.io/coreos/prometheus-operator@sha256:3daa69a8c6c2f1d35dcf1fe48a7cd8b230e55f5229a1ded438f687debade5bcf

How reproducible:
always


Steps to Reproduce:
1. Enable the `olm` when building the OCP 3.11, as below:
openshift_ansible_vars:
  openshift_enable_olm: true

Or, you can install it via run a playbook:
ansible-playbook -i qe-inventory-host-file playbooks/olm/config.yml

2. Login the Web console as a admin user.
3. Click the console link in the "openshift-console" namespace.
4. Click "Operators" >  "Catalog Sources"
5. For the Prometheus services, click "Create Subscription"
6. In the yaml editor, click "Create"
7. Click "Operators" > "Cluster Service Versions"
8. Click "View Instances" on Prometheus
9. Click "Create New" > "Prometheus"
10. Click "Create"
11. On the prometheus view, click "example" to go to the details of the prometheus just created.

Actual results:
Prometheus status is "unknown" and the only resource listed under "Resources" is a StatefulSet.

Expected results:
Should see the status transition to succeeded, and should be able to click on "Resources" and see the pods that prometheus creates.


Additional info:
This is an issue with the prometheus operator and not OLM itself. When prometheus operator is updated, OLM will package it and update in openshift-ansible.
Comment 1 Evan Cordell 2018-08-13 20:12:36 UTC 
This should be fixed in: https://github.com/openshift/openshift-ansible/pull/9564
Comment 4 Junqi Zhao 2018-08-23 07:43:57 UTC 
Change back to MODIFIED since PR is not merged
Comment 6 Junqi Zhao 2018-09-07 06:10:11 UTC 
# openshift version
openshift v3.11.0-0.28.0

It is able to create prometheus services via OLM, and be able to click on "Resources" and see the pods that prometheus creates. 

There is one little defect in UI, Prometheus status is Unknown in cluster web UI.see Bug 1626345
Comment 8 errata-xmlrpc 2018-10-11 07:24:38 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-2018:2652