Description of problem: Set "openshift_cluster_monitoring_operator_install: true" to deploy cluster monitoring along with OCP(not install cluster monitoring on an existing OCP env), cluster monitoring is not installed. Find in playbooks/common/openshift-cluster/upgrades/upgrade_components.yml - import_playbook: ../../../openshift-monitoring/private/config.yml when: openshift_monitoring_deploy | default(false) | bool and set "openshift_monitoring_deploy: true" to deploy cluster monitoring along with OCP would be successful It is better to change from when: openshift_monitoring_deploy | default(false) | bool to when: openshift_cluster_monitoring_operator_install | default(false) | bool in playbooks/common/openshift-cluster/upgrades/upgrade_components.yml Version-Release number of selected component (if applicable): openshift-ansible-3.11.0-0.19.0.git.0.ebd1bf9None.noarch.rpm openshift-ansible-docs-3.11.0-0.19.0.git.0.ebd1bf9None.noarch.rpm openshift-ansible-playbooks-3.11.0-0.19.0.git.0.ebd1bf9None.noarch.rpm openshift-ansible-roles-3.11.0-0.19.0.git.0.ebd1bf9None.noarch.rpm How reproducible: Always Steps to Reproduce: 1. Deploy cluster monitoring along with OCP 2. 3. Actual results: Inconsistent setting for deploy cluster monitoring Expected results: Additional info:
We have a pull request out to unify this: https://github.com/openshift/openshift-ansible/pull/9727
The pull request for this has been merged. https://github.com/openshift/openshift-ansible/pull/9727
Please change to ON_QA, it use openshift_cluster_monitoring_operator_install parameter to deploy cluster monitoring along with OCP or on one existing OCP env # rpm -qa | grep ansible openshift-ansible-docs-3.11.0-0.25.0.git.0.7497e69.el7.noarch openshift-ansible-roles-3.11.0-0.25.0.git.0.7497e69.el7.noarch openshift-ansible-3.11.0-0.25.0.git.0.7497e69.el7.noarch ansible-2.6.3-1.el7ae.noarch openshift-ansible-playbooks-3.11.0-0.25.0.git.0.7497e69.el7.noarch
Per Comment 3, set to VERIFIED
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