Searching and researching this topic, it seems that this issue has been raised on several places. Still, I haven't seen a resolution yet.
It seems that this problem arises whenever you try to make Ansible talk to a machine that has it's own shell behind ssh. It's my personal opinion that Ansible would become more valuable if you can make it talk to these kind of devices, like cisco routers and ILO cards, for change orchestration. -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/9d93f4fb-2b8e-4fe3-b8e0-91ebecc30c0b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
