This issue was certainly fixed when trusty got juju 1.20.11.
** Changed in: juju-core (Ubuntu Trusty)
Status: Confirmed => 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/1330406
This issue was certainly fixed when trusty got juju 1.20.11.
** Changed in: juju-core (Ubuntu Trusty)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: juju-core (Ubuntu Trusty)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: juju-core (Ubuntu Trusty)
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/1330406
Assuming this affects 1.18.4 in Trusty, adding a task to track that.
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Also affects: juju-core (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu)
Status: New = Fix
Assuming this affects 1.18.4 in Trusty, adding a task to track that.
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Also affects: juju-core (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu)
Status: New = Fix
