Bug 1543625 – [free-stg] error during upgrade if non yaml configmap with logging-es prefix exists

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

Bug 1543625 - [free-stg] error during upgrade if non yaml configmap with logging-es prefix exists

Summary:	[free-stg] error during upgrade if non yaml configmap with logging-es prefix ...

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Installer (Show other bugs)
Sub Component:
Version:	3.9.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	3.9.0
Assigned To:	ewolinet
QA Contact:	Anping Li
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2018-02-08 15:31 EST by Justin Pierce
Modified:	2018-03-28 10:27 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	Cause: Non-yaml formatted file was read in for configmap parsing based on the name matching other logging-es configmaps Consequence: The file is attempted to be parsed even if it is not in yaml format. Fix: We only try to parse the file if it is in yaml format. Result: We do not fail out due to not being able to parse a yaml file.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-03-28 10:27:28 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)
Example error output (4.25 KB, text/plain) 2018-02-08 15:31 EST, Justin Pierce	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2018:0489	None	None	None	2018-03-28 10:27 EDT

Groups: None (edit)

Description Justin Pierce 2018-02-08 15:31:50 EST

Created attachment 1393415 [details]
Example error output

Description of problem:

If a configmap exists in the logging namespace with non-yaml content, the logging upgrade playbooks try to parse the content as yaml and throw an error.

Version-Release number of the following components:
openshift v3.9.0-0.41.0

How reproducible:
100%

Steps to Reproduce:
1. Create  configmap/logging-es-kopf-config in logging namespace and populate it with non-yaml content
2. Run the logging upgrade playbook

Comment 2 ewolinet 2018-02-08 16:34:22 EST

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

Comment 6 Anping Li 2018-02-26 04:57:38 EST

Verified and pass using openshift-ansible-3.9.0-0.53

Comment 9 errata-xmlrpc 2018-03-28 10:27:28 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:0489

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