Description of problem: logging-curator fails to run following cluster logging upgrade to v3.11.374 $ oc -n openshift-logging logs logging-curator-1611822600-jp2mh 2021-01-28 08:30:13,271 INFO Found curator configuration in [/etc/curator/settings/config.yaml] 2021-01-28 08:30:13,278 INFO Converting config file. Traceback (most recent call last): File "/usr/bin/curator", line 9, in <module> load_entry_point('elasticsearch-curator==5.2.0', 'console_scripts', 'curator')() File "/usr/lib/python2.7/site-packages/click/core.py", line 722, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python2.7/site-packages/click/core.py", line 697, in main rv = self.invoke(ctx) File "/usr/lib/python2.7/site-packages/click/core.py", line 895, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/lib/python2.7/site-packages/click/core.py", line 535, in invoke return callback(*args, **kwargs) File "/usr/lib/python2.7/site-packages/curator/cli.py", line 211, in cli run(config, action_file, dry_run) File "/usr/lib/python2.7/site-packages/curator/cli.py", line 158, in run client = get_client(**client_args) File "/usr/lib/python2.7/site-packages/curator/utils.py", line 800, in get_client 'Error: {0}'.format(e) elasticsearch.exceptions.ElasticsearchException: Unable to create client connection to Elasticsearch. Error: 'module' object has no attribute 'ensure_str' Version-Release number of selected component (if applicable): 3.11.374 How reproducible: always (every time the curator job is run) Steps to Reproduce: 1. upgrade Cluster Logging (or just the curator image) to v3.11.374 2. logging-curator pod fails, streaming an `Unable to create client connection to Elasticsearch. Error: 'module' object has no attribute 'ensure_str'` in the pod logs. Additional info: - Rolling back [0] to a previous Curator image (i.e. v3.11.346, v3.11.272) works as temporary workaround: $ oc -n openshift-logging get pods NAME READY STATUS RESTARTS AGE logging-curator-1611822600-jp2mh 0/1 Error 0 26m logging-curator-1611824100-wlnn8 0/1 Completed 0 57s $ oc -n openshift-logging get pod -l component=curator -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.spec.containers[*].image}{"\n"}{end}' logging-curator-1611822600-jp2mh registry.redhat.io/openshift3/ose-logging-curator5:v3.11 logging-curator-1611824100-wlnn8 registry.redhat.io/openshift3/ose-logging-curator5:v3.11.272 [0] https://access.redhat.com/solutions/3749401
Fixied in v3.11.380.
Hi All, Is there a possibility someone can clarify the work around in access While trying to pull the ealier images to resolve the issue: oc import-image registry.redhat.io/openshift3/ose-logging-curator5:v3.11.59 error: the tag "v3.11.59" does not exist on the image stream - choose an existing tag to import or use the 'tag' command to create a new tag Even when pulling 380, it claims not to exist: oc import-image registry.redhat.io/openshift3/ose-logging-curator5:v3.11.380 error: the tag "v3.11.380" does not exist on the image stream - choose an existing tag to import or use the 'tag' command to create a new tag I can pull 347 correctly
I do not have any input into rebuilding of images but my suspicion is we will not be rebuilding 3.11.374 but recommend the customer upgrade directly to 3.11.380. Setting to no doctext as I was not involved in verifying the resolution .
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 (OpenShift Container Platform 3.11.380 bug fix and enhancement update), 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-2021:0274