Comment 5 for bug 1571612

I have to retract my comments above and the errors I was experiencing. Perhaps the other user was having more complex related issues, however mine was relatively simple once I discovered that I was running the incorrect version of Ansible. Since Kolla is highly opinionated about which version of Ansible is being used (and understandably-so), once I removed the previous version of ansible and used 1.9.4 (pip install ansible==1.9.4) everything started working just fine. If you use Ansible version 2.0 or higher, you will get the errors I mentioned earlier.

Even if this isn't related exactly to this issue...at least it may help someone trying to search for an answers.