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

Bug 1543625

Summary: [free-stg] error during upgrade if non yaml configmap with logging-es prefix exists
Product: OpenShift Container Platform Reporter: Justin Pierce <jupierce>
Component: InstallerAssignee: ewolinet
Status: CLOSED ERRATA QA Contact: Anping Li <anli>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.9.0CC: anli, aos-bugs, jokerman, jupierce, mmccomas, pportant
Target Milestone: ---   
Target Release: 3.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
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 14:27:28 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
Example error output none

Description Justin Pierce 2018-02-08 20:31:50 UTC
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 6 Anping Li 2018-02-26 09:57:38 UTC
Verified and pass using openshift-ansible-3.9.0-0.53

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