lp:juju-core/trunk r2644 broke 1.19.1
John Meinel
john at arbash-meinel.com
Fri Apr 18 12:39:02 UTC 2014
Note also that you're at your 20 instance limit in EC2. From what I can
tell you have a bunch of leaked manually provisioned machines, (looking at
euca-describe-instances and seeing what GROUP or job_name they have.)
2 in "default" group
7 in "manual-juju-test"
7 in juju-juju-ci3-* machines (presumably this is an actual Juju
environment named juju-ci3)
And some other random ones, like Jenkins itself.
John
=:->
On Thu, Apr 17, 2014 at 8:59 PM, Curtis Hovey-Canonical <
curtis at canonical.com> wrote:
> lp:juju-core/trunk r2644 introduced a regression.
> upgrade-juju fails on all providers
> https://bugs.launchpad.net/juju-core/+bug/1309108
>
> Unit agents are not upgrading. I attacked logs from all the failed tests.
>
> --
> Curtis Hovey
> Canonical Cloud Development and Operations
> http://launchpad.net/~sinzui
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140418/ddb480ee/attachment.html>
More information about the Juju-dev
mailing list