This should be a very short blog post, but long enough to justify a blog post instead of a 'tweet' : I had myself a small issue with mitogen plugin in our Ansible infra.
To cut a long story short, everybody knows that ansible relies on ssh as transport. So one can use traditional ~/.ssh/config tuning to declare ProxyJump for some hosts, etc
But when you use mitogen (we do), in the official doc there is a mention of specific parameter for connection delegation :
The simple example on the webpage seems trivial and if you have multiple hosts that need to be configured from remote ansible+mitogen combo, using mitogen would speed things up as it would know about the host topology.
That's what I thought when having a look at the simple inventory on that web page:
[dc2] web1.dc2 web2.dc2 web3.dc2 [dc2:vars] mitogen_via = bastion.dc2
Sounds easy but when I tried quickly to use mitogen_via , something that I thought would be obvious in fact wasn't.
My understanding was that mitogen would automatically force agent forwarding when going through the bastion host.
ansible -m ping (let's assume web1.dc2 in their example) returned …