Just as a follow up here, we don't recommend running the very latest devel
Ansible with Tower--we'd suggest sticking to the officially-released
versions. There's no reason why it shouldn't work, but you may run into
issues that our test matrix doesn't catch.
If you're just looking for new or updat
Thank you Sean, your suggestion worked for me and saved me time. Cheers.
On Wednesday, March 4, 2015 at 12:31:19 AM UTC-5, Sean Herrala wrote:
>
> In case anyone sees this and wants an actual answer, the problem is that
> the 'sanity check' in the configure script that does a version check looks
In case anyone sees this and wants an actual answer, the problem is that
the 'sanity check' in the configure script that does a version check looks
for the -1 index of the first line of the stdout of ansible --version,
and when you run from source, instead of that line being 'ansible 1.9',
it's
