Bug 1519622 – Disable DC rollback behaviors for logging project DCs

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1519622 - Disable DC rollback behaviors for logging project DCs

Summary:	Disable DC rollback behaviors for logging project DCs

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Logging (Show other bugs)
Sub Component:
Version:	3.7.0
Hardware:	All Linux

Priority	high Severity high
Target Milestone:	---
Target Release:	3.7.z
Assigned To:	Jeff Cantrill
QA Contact:	Anping Li
Docs Contact:

URL:
Whiteboard:
Keywords:	OpsBlocker

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-11-30 22:41 EST by Peter Portante
Modified:	2018-01-23 12:58 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:	Feature: Modify Elasticsearch deploymentconfigs to disable Openshift rollback behavior Reason: Upgrades of the logging stack that do not result in readiness probe succeeding are rolled back to the last previous successful deployment. This can result in the deployed instances being out-of-date with their configuration and old images Result: This changes will make it so the deployments will not be rolled back and operators can manually intervene without the image and configuration mismatches.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-01-23 12:58:09 EST
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
Github	openshift/openshift-ansible/pull/6356	None	None	None	2017-12-05 11:42 EST
Github	openshift/openshift-ansible/pull/6409	None	None	None	2017-12-08 14:18 EST
Red Hat Product Errata	RHBA-2018:0113	normal	SHIPPED_LIVE	OpenShift Container Platform 3.7 and 3.6 bug fix and enhancement update	2018-01-23 17:55:59 EST

Groups: None (edit)

Description Peter Portante 2017-11-30 22:41:12 EST

It seems we consider disabling the auto rollback to a "working" DC version when a rollout fails.

We can do that by adding, "revisionHistoryLimit: 0" to all logging project DCs.

The problem scenario is as follows:

  1. DC version X depends on configmap "version" A
  2. An upgrade is performed modifying the configmap to "version" B, and DC to version Y
  3. Version of Y of the DC is rolled out, but fails for some reason
  4. Because of the rollout failure, the DC rolls back to version X
  5. Now DC version X fails because the corresponding configmap "version" A is no longer present

Comment 1 openshift-github-bot 2017-12-08 14:17:01 EST

Commits pushed to master at https://github.com/openshift/openshift-ansible

https://github.com/openshift/openshift-ansible/commit/415fc54d7b44be4a1ee3cc63233c3bd8b031bdb2
bug 1519622. Disable rollback of ES DCs

https://github.com/openshift/openshift-ansible/commit/7b4c6781a680175fa985edab92c73cb3fc662073
Merge pull request #6356 from jcantrill/1519622_disable_revision_history

bug 1519622. Disable rollback of ES DCs

Comment 3 Anping Li 2017-12-18 21:43:02 EST

This fix is not merged to v3.7. and please move the bug to a installer errata too.

Comment 4 Anping Li 2018-01-10 23:37:50 EST

Please ignore comment 3, the fix is in openshift-ansible-3.7.22-1.git.0.a938a52.el7.noarch. The errata include both installer and package now.

Comment 5 Anping Li 2018-01-11 21:05:40 EST

The test is blocked by 1533313

Comment 6 Anping Li 2018-01-14 23:40:14 EST

Verified with openshift-ansible-3.7.23.

Comment 9 errata-xmlrpc 2018-01-23 12:58:09 EST

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:0113

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