Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1619505 - Inconsistent setting for deploy cluster monitoring
Inconsistent setting for deploy cluster monitoring
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring (Show other bugs)
3.11.0
Unspecified Unspecified
medium Severity medium
: ---
: 3.11.0
Assigned To: Frederic Branczyk
Junqi Zhao
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-08-21 01:13 EDT by Junqi Zhao
Modified: 2018-10-11 03:25 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-10-11 03:25:25 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2652 None None None 2018-10-11 03:25 EDT

  None (edit)
Description Junqi Zhao 2018-08-21 01:13:29 EDT
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:
Comment 1 Frederic Branczyk 2018-08-27 12:48:46 EDT
We have a pull request out to unify this: https://github.com/openshift/openshift-ansible/pull/9727
Comment 2 Frederic Branczyk 2018-08-27 20:20:46 EDT
The pull request for this has been merged. https://github.com/openshift/openshift-ansible/pull/9727
Comment 3 Junqi Zhao 2018-08-30 01:45:04 EDT
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
Comment 4 Junqi Zhao 2018-09-02 20:32:37 EDT
Per Comment 3, set to VERIFIED
Comment 6 errata-xmlrpc 2018-10-11 03:25:25 EDT
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

Note You need to log in before you can comment on or make changes to this bug.