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.
This should be fixed in: https://github.com/openshift/openshift-ansible/pull/9564
Change back to MODIFIED since PR is not merged
# 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
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