This will be handled only in the switch to Ansible 2.0.
It will not be fixed in Liberty or Mitaka unfortunately since it is an Ansible bug
This will be handled only in the switch to Ansible 2.0.
It will not be fixed in Liberty or Mitaka unfortunately since it is an Ansible bug