Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1752532

Summary: upgrade from 3.11 failed to upgrade es settings from configmap
Product: OpenShift Container Platform Reporter: Rajnikant <rkant>
Component: LoggingAssignee: Rich Megginson <rmeggins>
Status: CLOSED ERRATA QA Contact: Anping Li <anli>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 3.11.0CC: alchan, aos-bugs, grodrigu, lvlcek, mburke, mirollin, mruzicka, nagrawal, rmeggins, stwalter, wsun
Target Milestone: ---   
Target Release: 3.11.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-18 01:34: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:
Attachments:
Description Flags
ansible logging upgrade elasticsearch config diffs none

Description Rajnikant 2019-09-16 15:01:28 UTC 
Description of problem:
elasticsearch container failed to start in logging cluster

Version-Release number of selected component (if applicable):
v3.11.117

How reproducible:
- While upgrading logging cluster to 3.11.117, failed while checking es pod to ready.


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 36 Rich Megginson 2019-09-17 19:49:41 UTC 
Created attachment 1615994 [details]
ansible logging upgrade elasticsearch config diffs
Comment 43 Anping Li 2019-10-12 07:33:14 UTC 
The old elasticsearch configmap are saved as logging-elasticsearch.old

$ oc get configmap
NAME                        DATA   AGE
logging-elasticsearch       2      1h
logging-elasticsearch.old   2      9m
Comment 45 errata-xmlrpc 2019-10-18 01:34: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-2019:3139