-
Which version of Ansible are you running?
ansible-2.6.5-1.el7.noarch
-
Is your version of Ansible patched in any way?
default upstream
-
Are you running with any custom modules, or module_utils loaded?
no
-
Have you tried the latest master version from Git?
no
-
Do you have some idea of what the underlying problem may be?
https://mitogen.rtfd.io/en/stable/ansible.html#common-problems has
instructions to help figure out the likely cause and how to gather relevant
logs.
It seems the pattern is the target arch : armhfp , while it works fine with other arches like x86_64, ppc64e, aarch64
Here is the log when trying to "ping" with ansible some armhfp nodes :
armhfp-01.sub.domain.com | UNREACHABLE! => {
"changed": false,
"msg": "EOF on stream; last 300 bytes received: u'n\n File "", line 552, in _profile_hook\n File "", line 3081, in _dispatch_calls\n File "", line 1035, in iter\n File "", line 1021, in get\n File "", line 2185, in get\n File "", line 2150, in _make_cookie\nerror: integer out of range for \'l\' format code'",
"unreachable": true
}
armhfp-03.sub.domain.com | UNREACHABLE! => {
"changed": false,
"msg": "EOF on stream; last 300 bytes received: u'n\n File "", line 552, in _profile_hook\n File "", line 3081, in _dispatch_calls\n File "", line 1035, in iter\n File "", line 1021, in get\n File "", line 2185, in get\n File "", line 2150, in _make_cookie\nerror: integer out of range for \'l\' format code'",
"unreachable": true
}
ERROR! [pid 25435] 16:49:32.020977 E mitogen.ctx.ssh.armhfp-01.domain.com: mitogen: ExternalContext.main() crashed
Traceback (most recent call last):
File "", line 3354, in main
File "", line 3093, in run
File "", line 552, in _profile_hook
File "", line 3081, in _dispatch_calls
File "", line 1035, in iter
File "", line 1021, in get
File "", line 2185, in get
File "", line 2150, in _make_cookie
error: integer out of range for 'l' format code
armhfp-02.domain.com | UNREACHABLE! => {
"changed": false,
"msg": "EOF on stream; last 300 bytes received: u'n\n File "", line 552, in _profile_hook\n File "", line 3081, in _dispatch_calls\n File "", line 1035, in iter\n File "", line 1021, in get\n File "", line 2185, in get\n File "", line 2150, in _make_cookie\nerror: integer out of range for \'l\' format code'",
"unreachable": true
}
armhfp-02.sub.domain.com | UNREACHABLE! => {
"changed": false,
"msg": "EOF on stream; last 300 bytes received: u'n\n File "", line 552, in _profile_hook\n File "", line 3081, in _dispatch_calls\n File "", line 1035, in iter\n File "", line 1021, in get\n File "", line 2185, in get\n File "", line 2150, in _make_cookie\nerror: integer out of range for \'l\' format code'",
"unreachable": true
}
armhfp-01.domain.com | UNREACHABLE! => {
"changed": false,
"msg": "Channel was disconnected while connection attempt was in progress; this may be caused by an abnormal Ansible exit, or due to an unreliable target.",
"unreachable": true
Worth noting that switching back to normal strategy through ansible.cfg permits to ping such nodes fine
Happy to give me details if needed
Which version of Ansible are you running?
ansible-2.6.5-1.el7.noarch
Is your version of Ansible patched in any way?
default upstream
Are you running with any custom modules, or
module_utilsloaded?no
Have you tried the latest master version from Git?
no
Do you have some idea of what the underlying problem may be?
https://mitogen.rtfd.io/en/stable/ansible.html#common-problems has
instructions to help figure out the likely cause and how to gather relevant
logs.
It seems the pattern is the target arch : armhfp , while it works fine with other arches like x86_64, ppc64e, aarch64
Mention your host and target OS and versions
CentOS 7 everywhere
Mention your host and target Python versions
same : python-2.7.5-76.el7.x86_64
Here is the log when trying to "ping" with ansible some armhfp nodes :
armhfp-01.sub.domain.com | UNREACHABLE! => {
"changed": false,
"msg": "EOF on stream; last 300 bytes received: u'n\n File "", line 552, in _profile_hook\n File "", line 3081, in _dispatch_calls\n File "", line 1035, in iter\n File "", line 1021, in get\n File "", line 2185, in get\n File "", line 2150, in _make_cookie\nerror: integer out of range for \'l\' format code'",
"unreachable": true
}
armhfp-03.sub.domain.com | UNREACHABLE! => {
"changed": false,
"msg": "EOF on stream; last 300 bytes received: u'n\n File "", line 552, in _profile_hook\n File "", line 3081, in _dispatch_calls\n File "", line 1035, in iter\n File "", line 1021, in get\n File "", line 2185, in get\n File "", line 2150, in _make_cookie\nerror: integer out of range for \'l\' format code'",
"unreachable": true
}
ERROR! [pid 25435] 16:49:32.020977 E mitogen.ctx.ssh.armhfp-01.domain.com: mitogen: ExternalContext.main() crashed
Traceback (most recent call last):
File "", line 3354, in main
File "", line 3093, in run
File "", line 552, in _profile_hook
File "", line 3081, in _dispatch_calls
File "", line 1035, in iter
File "", line 1021, in get
File "", line 2185, in get
File "", line 2150, in _make_cookie
error: integer out of range for 'l' format code
armhfp-02.domain.com | UNREACHABLE! => {
"changed": false,
"msg": "EOF on stream; last 300 bytes received: u'n\n File "", line 552, in _profile_hook\n File "", line 3081, in _dispatch_calls\n File "", line 1035, in iter\n File "", line 1021, in get\n File "", line 2185, in get\n File "", line 2150, in _make_cookie\nerror: integer out of range for \'l\' format code'",
"unreachable": true
}
armhfp-02.sub.domain.com | UNREACHABLE! => {
"changed": false,
"msg": "EOF on stream; last 300 bytes received: u'n\n File "", line 552, in _profile_hook\n File "", line 3081, in _dispatch_calls\n File "", line 1035, in iter\n File "", line 1021, in get\n File "", line 2185, in get\n File "", line 2150, in _make_cookie\nerror: integer out of range for \'l\' format code'",
"unreachable": true
}
armhfp-01.domain.com | UNREACHABLE! => {
"changed": false,
"msg": "Channel was disconnected while connection attempt was in progress; this may be caused by an abnormal Ansible exit, or due to an unreliable target.",
"unreachable": true
Worth noting that switching back to normal strategy through ansible.cfg permits to ping such nodes fine
Happy to give me details if needed