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 ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.9.0
Assignee: ewolinet
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-08 20:31 UTC by Justin Pierce
Modified: 2018-03-28 14:27 UTC (History)
6 users (show)

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.
Clone Of:
Environment:
Last Closed: 2018-03-28 14:27:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Example error output (4.25 KB, text/plain)
2018-02-08 20:31 UTC, Justin Pierce
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0489 0 None None None 2018-03-28 14:27:56 UTC

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


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