This is unfortunate, but it is a bug with Ansible 1.x. This bug is fixed in Ansible 2.x, but our playbooks are not compatible with 2.x
In the newton cycle we will fix this issue indirectly by switching to Ansible 2.x.
This is unfortunate, but it is a bug with Ansible 1.x. This bug is fixed in Ansible 2.x, but our playbooks are not compatible with 2.x
In the newton cycle we will fix this issue indirectly by switching to Ansible 2.x.