Package: ansible-mitogen
Version: 0.3.3-9
Severity: important
Hi,
I tried to upgrade a debian machine to trixie (one managed by ansible
but not the one where ansible is run) and then replay various ansible
playbook on this machine.
As soon as the ssh connection is tried, ansible fails with the following
message:
[mux 3252361] 13:28:21.588951 D mitogen.parent: creating connection to context
2 using mitogen.ssh
[mux 3252361] 13:28:21.621393 D mitogen.parent: command line for
Connection(None): ssh -o "LogLevel ERROR" -l vdanjean-ansible-client -o
"Compression yes" -o "ServerAliveInterval 30" -o "ServerAliveCountMax 10" -o
"BatchMode yes" -o "StrictHostKeyChecking yes" -C -o ControlMaster=auto -o
ControlPersist=60s belgarath /usr/bin/python3 -c "'import
codecs,os,sys;_=codecs.decode;exec(_(_(\"eNqVkl9PwjAUxd/5FL7dNi7QlghhcYkEUEzkTxZ0MbgsHStahW7pgImf3o4Z2PDB+NZfz7n3nq3XtTwnTuuJTATCNW1lJZLLCwPLWH8gbNfyc7RNGCIWJQSf2LXKpI1KC16s4lQgtwy6DF4ZMgPFwK3iazN+TnzHgT7XmVTAVVSWmD+3mX8NtHNQ0n1aF59isd3wcCVMVWOb6kYoVSPZb95iBfaZ49zA6m3493hzzwijxwQ7oVMZq7ndzCvzlrapEWontbmF6fNsOBkHD93HcW846Ae37mQUeG53Oh244DtA4fA3jv6ue/dEjFCNXngMrlBVsKp4CWgtN/GrUPYu4updcHXD99xusivWbFEMuGYaZVpuBKIWjO5nE0LIiwITYBFH5itxrecEKF+AKE6EMs8OOgRc14JHiLZJp4Ut+JKJ6bRMnJPPsyALId+JZfIzoHc4F+985s7+cv9OSaspjxvE8DcLquFw\".encode(),\"base64\"),\"zip\"))'"
[task 3252404] 13:28:21.587430 D ansible_mitogen.process: will use multiplexer
0 (/tmp/mitogen_unix_s_9t36ts.sock) to connect to "belgarath"
[task 3252404] 13:28:21.587571 D mitogen.unix: client: connecting to
/tmp/mitogen_unix_s_9t36ts.sock
[task 3252404] 13:28:21.587730 D mitogen.unix: client: local ID is 1, remote is 0
[task 3252404] 13:28:21.853576 D ansible_mitogen.mixins: _remove_tmp_path(None)
[task 3252404] 13:28:21.853735 D mitogen:
MitogenProtocol(unix_listener.3252361): disconnecting
[task 3252404] 13:28:21.853850 D mitogen: Waker(fd=11/12): disconnecting
[task 3252404] 13:28:21.853967 D mitogen: Router(Broker(f510)): stats: 0 module
requests in 0 ms, 0 sent (0 ms minify time), 0 negative responses. Sent 0.0 kb
total, 0.0 kb avg.
fatal: [belgarath]: UNREACHABLE! => {
"changed": false,
"msg": "EOF on stream; last 100 lines
received:\nMITO000\nMITO001\nTraceback (most recent call last):\n File
\"<stdin>\", line 63, in <module>\nModuleNotFoundError: No module named 'imp'",
"unreachable": true
}
This is due to the fact that python3 3.13 on the targeted machine (trixie)
does not have the imp module anymore. Changing the strategy to linear (instead
of mitogen_linear) workaround the problem (at the expense of not using mitogen
anymore).
Even if it is difficult to update the bookworm package, if a simple patch
exists to fix the bookworm version, it would be welcome in order to avoid
the need to upgrade the ansible machine before any others (or to disable
mitogen).
Regards,
Vincent
PS: as soon as I get the bug number, I will mark it fixed in the 0.3.25~a1-1
version.
-- System Information:
Debian Release: 12.11
APT prefers oldstable-updates
APT policy: (990, 'oldstable-updates'), (990, 'oldstable-security'), (990,
'oldstable'), (500, 'oldoldstable-updates'), (500, 'oldoldstable-security'),
(500, 'oldoldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.12.32+bpo-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages ansible-mitogen depends on:
ii ansible 7.7.0+dfsg-3+deb12u1
ii ansible-core 2.14.18-0+deb12u2
ii python3 3.11.2-1+b1
ii python3-mitogen 0.3.3-9
ansible-mitogen recommends no packages.
ansible-mitogen suggests no packages.
-- no debconf information
