Bug 1627689
| Summary: | The elasticsearch-config should be logging-elasticsearch-ops in logging-es-ops pods | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Anping Li <anli> |
| Component: | Logging | Assignee: | Jeff Cantrill <jcantril> |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.11.0 | CC: | aos-bugs, ewolinet, qitang, rmeggins |
| Target Milestone: | --- | ||
| Target Release: | 3.11.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: The installer did not parameterize the configmap used by the ES pods
Consequence: The ops ES pods used the configmap of the non-ops ES pods
Fix: Parameterize the template used by the installer
Result: The ES ops pods use the logging-es-ops configmap
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-11-20 03:10:43 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: | |||
Moved this to a z-stream as the expectation is it affects a small number of customers if any at all. Verified with:
openshift-ansible-docs-3.11.36-1.git.0.2213c76.el7.noarch
ansible-2.6.5-1.el7ae.noarch
openshift-ansible-playbooks-3.11.36-1.git.0.2213c76.el7.noarch
openshift-ansible-3.11.36-1.git.0.2213c76.el7.noarch
openshift-ansible-roles-3.11.36-1.git.0.2213c76.el7.noarch
# oc exec -c elasticsearch logging-es-ops-data-master-eisqwbuv-1-v5g4r -- head -6 /etc/elasticsearch/elasticsearch.yml
cluster:
name: ${CLUSTER_NAME}
discovery.zen:
minimum_master_nodes: ${NODE_QUORUM}
ping.unicast.hosts: logging-es-ops-cluster
gateway:
# oc get dc logging-es-ops-data-master-eisqwbuv -o yaml |grep -A 3 configMap
- configMap:
defaultMode: 420
name: logging-elasticsearch-ops
name: elasticsearch-config
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:3537 |
Description of problem: The configmap are logging-elasticsearch in logging-es-ops deploymentconfig. As a result, the ping.unicast.hosts is logging-es-cluster in elasticsearch.yml. That made the logging-es-ops pods couldn't be started. #oc rsh logging-es-ops-data-master-k06vkabq-1-kn9mr head -6 /etc/elasticsearch/elasticsearch.yml cluster: name: ${CLUSTER_NAME} discovery.zen: minimum_master_nodes: ${NODE_QUORUM} ping.unicast.hosts: logging-es-cluster Version-Release number of selected component (if applicable): openshift-ansible:v3.11.0-0.32.0 How reproducible: always Steps to Reproduce: 1. deploy logging and enable logging-ops openshift_logging_install_logging=true openshift_logging_use_ops=true 2. Check the elasticsearch-config in logging-es-ops deploymengconfig $ oc get dc logging-es-ops-data-master-o7f0q18m -o yaml |grep -A 3 configMap - configMap: defaultMode: 420 name: logging-elasticsearch name: elasticsearch-config 3. check the elasticsearch.yml oc rsh logging-es-ops-data-master-k06vkabq-1-kn9mr head -6 /etc/elasticsearch/elasticsearch.yml cluster: name: ${CLUSTER_NAME} discovery.zen: minimum_master_nodes: ${NODE_QUORUM} ping.unicast.hosts: logging-es-cluster Actual results: The ping.unicast.hosts is logging-es-cluster. The logging-es-ops pods are using elasticsearch.yml from logging-elasticsearch configmap Expected results: The ping.unicast.hosts is logging-es-ops-cluster. The logging-es-ops pods should use elasticsearch.yml from logging-elasticsearch-ops configmap Additional info: