Description of problem: 2017-03-21 11:13:10.685 1033426 ERROR ceilometer.agent.manager File "/usr/lib/python2.7/site-packages/retrying.py", line 217, in call 2017-03-21 11:13:10.685 1033426 ERROR ceilometer.agent.manager attempt = Attempt(fn(*args, **kwargs), attempt_number, False) 2017-03-21 11:13:10.685 1033426 ERROR ceilometer.agent.manager File "/usr/lib/python2.7/site-packages/ceilometer/coordination.py", line 227, in extract_my_subset 2017-03-21 11:13:10.685 1033426 ERROR ceilometer.agent.manager if hr.get_node(str(v)) == self._my_id] 2017-03-21 11:13:10.685 1033426 ERROR ceilometer.agent.manager UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 66: ordinal not in range(128) Version-Release number of selected component (if applicable): RHOS 10 Steps to Reproduce: 1. not sure 2. 3. Actual results: The previous trace Expected results: no trace Additional info:
Created attachment 1265066 [details] error on horizon
I am backporting the patch to stable/newton upstream and will release a new Ceilometer version as soon as it's merged.
There is something out there that is not ASCII unfortunately. I don't know what it is but it might be well hidden. I've sent a patch upstream to release Ceilometer 7.0.3 with that fix: https://review.openstack.org/448254 Pradeep, I handle it to you to be sure the package is updated and pushed downstream.
The upstream release is out.
*** Bug 1437938 has been marked as a duplicate of this bug. ***
Hello, Any ETA for this 7.0.3 package in RDO/Newton ? Best regards, Edouard
RDO already have 7.0.4 https://cbs.centos.org/koji/buildinfo?buildID=17172
Sorry I meant an ETA for RDO/Newton repo. Can't find in it.
Package 7.0.3 is ready for RDO too, I have no idea why it's not promoted to the stable repo yet. You should ask support with RDO folks instead of here.
You can check the newton trunk repo: https://trunk.rdoproject.org/centos7-newton/current/, the package is there too.
Tested, the non-legal character doesn't cause errors in ceilometer anymore
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-2017:1586