Fix released in the Ansible 2.0.0.2-2ubuntu1.3 package.
** Changed in: ansible (Ubuntu Xenial)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836961
Title:
** Changed in: ansible (Ubuntu Xenial)
Assignee: (unassigned) => Paulo Flabiano Smorigo (pfsmorigo)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836961
Title:
ansible 2.0.0.2-2ubuntu1.2
** Also affects: ansible (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: ansible (Ubuntu)
Status: Confirmed => Invalid
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ansible (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836961
Title:
I've rolled xenial-updates and xenial-security back to ansible
2.0.0.2-2ubuntu1.1 to mitigate the breakage for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836961
Title:
ansible
We are seeing the same behavior on 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836961
Title:
ansible 2.0.0.2-2ubuntu1.2 uninstallable on Ubuntu 16.04
To manage notifications about this
