thumper, axw and I spent quite a bit of time on this on Friday and think we
know what's happening (nothing to do with the API logins change). The
potential fix is here:

https://github.com/juju/juju/pull/188


On 27 June 2014 12:22, Menno Smits <[email protected]> wrote:

> I'm currently taking a look at #1334273. It could be related to the
> "restricted API logins during upgrades" change I made.
>
>
> On 27 June 2014 06:00, Curtis Hovey-Canonical <[email protected]>
> wrote:
>
>> We are tracking a list of critical bugs that must be fixed to release
>> 1.20.
>>     https://launchpad.net/juju-core/+milestone/1.20.0
>>
>> I intend to create a 1.20 branch in
>>     https://github.com/juju/juju
>> that we can merge fixes into. Actually I have done that, but github
>> doesn't want me to merge by version branch...I need to tinker with the
>> issue to resolve it.
>>
>> I think the 1.20 branch needs to be version 1.20.0
>> I propose we set the master branch to 1.21-alpha1 now so that
>> development can continue to add new features.
>>
>> --
>> Curtis Hovey
>> Canonical Cloud Development and Operations
>> http://launchpad.net/~sinzui
>>
>> --
>> Juju-dev mailing list
>> [email protected]
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>
>
>
-- 
Juju-dev mailing list
[email protected]
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Reply via email to