Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1498989 - Change to remove automatic deployment triggers in deploymentconfigs
Change to remove automatic deployment triggers in deploymentconfigs
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging (Show other bugs)
3.7.0
All All
high Severity high
: ---
: 3.7.z
Assigned To: ewolinet
Junqi Zhao
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2017-10-05 14:30 EDT by Peter Portante
Modified: 2018-04-05 05:30 EDT (History)
7 users (show)

See Also:
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 05:29:37 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)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0636 None None None 2018-04-05 05:30 EDT

  None (edit)
Description Peter Portante 2017-10-05 14:30:43 EDT 
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 2 ewolinet 2017-12-15 11:49:22 EST 
3.7 release https://github.com/openshift/openshift-ansible/pull/6491
Comment 5 Junqi Zhao 2018-02-14 03:13:17 EST 
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 05:29:37 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:0636
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.