Bug 1726717 - EFK fails to upgrade because 'unicode' object has no attribute 'iteritems'
Summary: EFK fails to upgrade because 'unicode' object has no attribute 'iteritems'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.11.z
Assignee: ewolinet
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-03 14:12 UTC by Borja Aranda
Modified: 2023-10-06 18:24 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-13 14:09:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift openshift-ansible pull 11771 0 None None None 2019-07-17 16:24:29 UTC
Red Hat Product Errata RHBA-2019:2352 0 None None None 2019-08-13 14:09:30 UTC

Comment 6 Russell Teague 2019-07-16 19:28:34 UTC 
Moving to logging team.
Comment 10 Anping Li 2019-08-07 10:00:31 UTC 
I can reproduce this bug and verify the fix in openshift3/ose-ansible:v3.11.135
Comment 11 Anping Li 2019-08-08 06:29:36 UTC 
@cstark 
@gferrazs

Although this bug is fixed. You still need to overcome https://bugzilla.redhat.com/show_bug.cgi?id=1738758 . and you may need to overcome https://bugzilla.redhat.com/show_bug.cgi?id=1738766. 
For BZ1738758, the workaround is to correct nodeSelector logging-es-ops the deploymentconfig while the logging-es pod is starting.
For BZ1738766, the workaround is rolling restart logging-es-ops pod manully after upgrade. https://docs.openshift.com/container-platform/3.11/install_config/aggregate_logging.html#manual-elasticsearch-rollouts
Comment 13 errata-xmlrpc 2019-08-13 14:09:19 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:2352
Note You need to log in before you can comment on or make changes to this bug.