Ansible-core 2.14 support

[vanyasvl]

Ansible-core 2.14.0 was released yesterday.

Please add support to mitogen.

Thanks.

[arrfab]

you're aware that #966 is still open so afaik mitogen doesn't support (yet) ansible-core 2.13 ... haven't checked in a while but still the reason why I stick with ansible-core 2.12 for the moment

[vanyasvl]

you're aware that #966 is still open so afaik mitogen doesn't support (yet) ansible-core 2.13 ... haven't checked in a while but still the reason why I stick with ansible-core 2.12 for the moment

Yep, so Mitogen project looks rather dead than alive

[apple4ever]

Yep, so Mitogen project looks rather dead than alive

It seems so. I filed #945 four months ago and we had to stop using it because of that. Nobody has even commented to try to help.

It's a shame because it was a great project and made Ansible so fast. But that's how it goes with open source. I'd love to contribute since I do know Python but I don't know enough to help in a project like this.

Yep, so Mitogen project looks rather dead than alive

It seems so. I filed #945 four months ago and we had to stop using it because of that. Nobody has even commented to try to help.

It's a shame because it was a great project and made Ansible so fast. But that's how it goes with open source. I'd love to contribute since I do know Python but I don't know enough to help in a project like this.

Actually the "fast" part should be inside ansible core. Why ansible core does not implement it is hard to understand.

[opoplawski]

FWIW - just bumping ANSIBLE_VERSION_MAX to (2, 14) allows my plays to run. YMMV.

[badfiles]

TASK [community.zabbix.zabbix_agent : Do a yum clean] ****************************************************************************************************************************************
fatal: [*mx.*.*]: FAILED! => {"changed": false, "msg": "Unsupported parameters for (ansible.legacy.command) module: warn. Supported parameters include: executable, argv, removes, chdir, _uses_shell, stdin_add_newline, stdin, strip_empty_ends, creates, _raw_params."}

it's broken with forced 2.14 support

[nerijus]

it's broken with forced 2.14 support

I have it without mitogen, removing warn helps, so it is not a mitogen problem.

[NikitaCOEUR]

FWIW - just bumping ANSIBLE_VERSION_MAX to (2, 14) allows my plays to run. YMMV.

I try it but gather fact failed with this..
So force use Ansible-core 2.12... (Ansible 5)

[arrfab]

FWIW - just bumping ANSIBLE_VERSION_MAX to (2, 14) allows my plays to run. YMMV.

Just curious .. myself I'd need to bump to 2.14 but mitogen is still the only thing that doesn't work with it .. can you elaborate on the ANSIBLE_VERSION_MAX ? you mean directly in mitogen and so bypass all checks ?

[opoplawski]

FWIW - just bumping ANSIBLE_VERSION_MAX to (2, 14) allows my plays to run. YMMV.

Just curious .. myself I'd need to bump to 2.14 but mitogen is still the only thing that doesn't work with it .. can you elaborate on the ANSIBLE_VERSION_MAX ? you mean directly in mitogen and so bypass all checks ?

Yes.

[amarao]

I ack that, I've run a rather big codebase on ansible-2.14 and mitogen with patched version restriction and it just worked.

May be we can allow users to override this restriction via environment variable or some other mechanism. End-user patching is madness.

[arrfab]

Yes, or better : have a new mitogen tag/release that would have that ? Wondering if a mitogen dev can consider this, assuming that there were enough feedback about it working with ansible-core 2.14 (or list what would still be problematic, etc)

@moreati : opinion on this ?

[krystian-panek-vmltech]

how about introducing some configuration parameter here

mitogen/ansible_mitogen/loaders.py

Line 54 in 8cda5f5

NEW_VERSION_MSG = (

for skipping that check / allowing to use Ansible Mitogen with Ansible not officially/tested/supported version? of course at own risk...

from my perspective using Mitogen is very valuable and it just decreases Ansible execution time by minutes for free it is just very sad that right now there is no Mitogen version officially compatible with any maintained Ansible version.

The most recent version of Ansible that works with Mitogen I found is 5.10.0:

I have no Python skills and I am unable to help but if there is sb that could help with making Mitogen up-to-date with some recent version of Ansible ... then I will not hesitate and buy such a person a beer ;)