Bug 1498989

Summary:	Change to remove automatic deployment triggers in deploymentconfigs
Product:	OpenShift Container Platform	Reporter:	Peter Portante <pportant>
Component:	Logging	Assignee:	ewolinet
Status:	CLOSED ERRATA	QA Contact:	Junqi Zhao <juzhao>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.7.0	CC:	aos-bugs, ewolinet, jcantril, jokerman, juzhao, mmccomas, rmeggins
Target Milestone:	---
Target Release:	3.7.z
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Feature: elasticsearch dcs are created without config change triggers Reason: to avoid the unplanned restart of elasticsearch pods which could cause loss of data Result: When a config change is made to an elasticsearch dc it is not automatically rolled out and can be done at a scheduled time. Docs have been updated to describe how this can be done.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-05 09:29:37 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 Peter Portante 2017-10-05 18:30:43 UTC

Right now, if a change is made to a deployment configuration, we Kube will redeploy the pod.  This is not necessarily desirable for Elasticsearch data nodes.

If we need to make a few changes, perhaps via an ansible script, ideally we'd want to have a handler collect all the "restarts" required and issue one restart, perhaps properly synchronized with all other ES cluster pods that need to be restarted.

Comment 1 ewolinet 2017-12-07 14:40:09 UTC

https://github.com/openshift/openshift-ansible/pull/6379

Comment 2 ewolinet 2017-12-15 16:49:22 UTC

3.7 release https://github.com/openshift/openshift-ansible/pull/6491

Comment 5 Junqi Zhao 2018-02-14 08:13:17 UTC

Tested with logging with enabled ops cluster, make changes to ES/ES-OPS dc, the ES/ES-OPS pods won't be redeployed.

env:

openshift-ansible-3.7.29-1.git.0.e1bfc35.el7.noarch.rpm
openshift-ansible-callback-plugins-3.7.29-1.git.0.e1bfc35.el7.noarch.rpm
openshift-ansible-docs-3.7.29-1.git.0.e1bfc35.el7.noarch.rpm
openshift-ansible-filter-plugins-3.7.29-1.git.0.e1bfc35.el7.noarch.rpm
openshift-ansible-lookup-plugins-3.7.29-1.git.0.e1bfc35.el7.noarch.rpm
openshift-ansible-playbooks-3.7.29-1.git.0.e1bfc35.el7.noarch.rpm
openshift-ansible-roles-3.7.29-1.git.0.e1bfc35.el7.noarch.rpm

Comment 9 errata-xmlrpc 2018-04-05 09:29:37 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:0636