From 4b30fa5635349de1247d7135161526f5ca36d47f Mon Sep 17 00:00:00 2001
From: Ian Wienand <iwienand@redhat.com>
Date: Fri, 10 Aug 2018 14:13:04 +1000
Subject: [PATCH] Bump ansible for linters

I noticed this when I tried to use Ansible 2.5 "loop:" constructs.

Unfortunately, we can't just rely on bringing in zuul to pull the
right version of ansible.  ansible-lint being uncapped just takes it
over, and we end up with the latest version.  Pin it to the current
zuul requirements and add a note (maybe one day
https://github.com/pypa/pip/issues/988 will get a fix ...)

Change-Id: Iaf8f0f5cdc46df41fec7c436c1179c80bb5c368e
---
 tox.ini | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/tox.ini b/tox.ini
index 430e318b10..a32975ba0c 100644
--- a/tox.ini
+++ b/tox.ini
@@ -22,7 +22,10 @@ passenv =
 deps =
      # Zuul is required to supply the zuul ansible modules for ansible-lint
      -egit+https://git.openstack.org/openstack-infra/zuul#egg=zuul
-     ansible<2.4.0
+     # Unfortunately pip doesn't do actual dependency resolution, so
+     # we need to manually ansible at the top level to the same as
+     # zuul requirements.txt
+     ansible>=2.5.1,<2.6
      ansible-lint
      hacking>=0.10,<0.11
      bashate>=0.2