Unicode-objects must be encoded before hashing

[Laurent Goussard]

My brand new ARM server, freshly installed refuse to be managaed by ansible.

As soon as I try to reach it, here is the error I get back :

ansible chronos -m ping -u root -k
SSH password:
chronos.du-jour.fr | UNREACHABLE! => {
    "changed": false,
    "msg": "Unicode-objects must be encoded before hashing",
    "unreachable": true
}Saisissez le code ici...

I use ansible 2.4 :

ansible 2.4.0.0
  config file = /Users/loranger/.ansible.cfg
  configured module search path = [u'/Users/loranger/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/Cellar/ansible/2.4.0.0/libexec/lib/python2.7/site-packages/ansible
  executable location = /usr/local/bin/ansible
  python version = 2.7.14 (default, Sep 25 2017, 09:54:19) [GCC 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.37)]

My other servers answers flawlessly, but not this one.

Did I miss something ?

[Toshio Kuratomi]

We'll need more information than this, I'm afraid.  I don't see anything in the information so far given that would explain what's happening.  What are some differences between the machine that's most like this one and the one having problems?

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscribe@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/7c977317-2a74-40a4-a349-603168b345f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Laurent Goussard]

Thank you Toshi

I'm sorry, but I haven't got a lot of informations :

My new server is an ARM based one, with a fresh debian 8 installed whereas the other ones are x86 running debian 8 too (but are already ansible' provisioned).

That's the only difference I could notice. The host is the same (OVH). Maybe the new server is using ipv6 whereas the other are ipv6 ready only, I have to check this.

Le mercredi 25 octobre 2017 23:18:45 UTC+2, Toshio Kuratomi a écrit :

We'll need more information than this, I'm afraid.  I don't see anything in the information so far given that would explain what's happening.  What are some differences between the machine that's most like this one and the one having problems?

On Oct 25, 2017 1:45 PM, "Laurent Goussard" <laur...@gmail.com> wrote:

My brand new ARM server, freshly installed refuse to be managaed by ansible.

As soon as I try to reach it, here is the error I get back :

ansible chronos -m ping -u root -k
SSH password:
chronos.du-jour.fr | UNREACHABLE! => {
    "changed": false,
    "msg": "Unicode-objects must be encoded before hashing",
    "unreachable": true
}Saisissez le code ici...

I use ansible 2.4 :

ansible 2.4.0.0
  config file = /Users/loranger/.ansible.cfg
  configured module search path = [u'/Users/loranger/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/Cellar/ansible/2.4.0.0/libexec/lib/python2.7/site-packages/ansible
  executable location = /usr/local/bin/ansible
  python version = 2.7.14 (default, Sep 25 2017, 09:54:19) [GCC 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.37)]

My other servers answers flawlessly, but not this one.

Did I miss something ?

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.

[Laurent Goussard]

It seems Ansible (via Paramiko) has issues with ED25519 SSH keys.

I temporarily disabled mine and it now works…