Ugh, this is happening in part because of a fix I just added I think. Somewhat strange that this is only triggering with non-ascii though. Although the code deals with encoding and decoding I would expect that dict vs string would be independent of whether the value was non-ascii.

I'll see if I can reproduce. If so I should be able to get out a quick fix.

Ugh. Okay, this is going to be a bit harder than I thought. I was able to fix the initial traceback rather quickly here: 35321ec

But that was just hiding the real error:

$ ansible-playbook utf8.yml                            *[devel]  (14:16:10)

PLAY [localhost] ************************************************************** 

GATHERING FACTS *************************************************************** 
ok: [localhost]

TASK: [Test utf] ************************************************************** 
fatal: [localhost] => {'msg': "UnicodeEncodeError: 'ascii' codec can't encode character u'\\xe9' in position 29: ordinal not in range(128)", 'failed': True}
fatal: [localhost] => {'msg': "UnicodeEncodeError: 'ascii' codec can't encode character u'\\xe9' in position 29: ordinal not in range(128)", 'failed': True}

FATAL: all hosts have already failed -- aborting

PLAY RECAP ******************************************************************** 
           to retry, use: --limit @/home/badger/utf8.retry

localhost                  : ok=1    changed=0    unreachable=1    failed=0

That commit should finish off the fix. I also tested this in the v2 tree and everything worked as expected there.

Closing This Ticket

Hi!

We believe recent commits (likely detailed above) should resolve this question or problem for you.

This will also be included in the next major release.

If you continue seeing any problems related to this issue, or if you have any further questions, please let us know by stopping by one of the two mailing lists, as appropriate:

• https://groups.google.com/forum/#!forum/ansible-project - for user questions, tips, and tricks
• https://groups.google.com/forum/#!forum/ansible-devel - for strategy, future planning, and questions about writing code

Because this project is very active, we're unlikely to see comments made on closed tickets, but the mailing list is a great way to ask questions, or post if you don't think this particular
issue is resolved.

Thank you!

Works on the devel branch for me, thanks ;)

Hello,

I'm still having issues with that on 2.5.1, as per #27262 that I opened last year. Anything I can do to help getting it fixed?

Thanks

Same on 2.5.2

@yodatak: it's been dealt with in #27262 and the fix has just been released in 2.5.3.