Comment 12 for bug 1509097

Hi Ian --

dpb@helo:bin[0]$ juju bootstrap -v --no-auto-upgrade
error: flag provided but not defined: --no-auto-upgrade
dpb@helo:bin[0]$ juju --version
1.24.7-vivid-amd64

I know about the trick of modifying the environment already which is what
we do in other situations, maybe we need to do that here for the dirty
workaround...

  agent-version: $(juju --version)

On Thu, Oct 22, 2015 at 8:56 PM, Ian Booth <email address hidden> wrote:

> What I recommend here is that:
>
> 1. the immediate issue can be solved for 1.24 and 1.25 by ensuring the
> --no-auto-upgrade arg is used
>
> 2. we will improve the behaviour of how auto upgrades are done for 1.26
>
> 3. in Juju 2.0, we will not auto upgrade by default
>
> --
> You received this bug notification because you are a member of
> Landscape, which is subscribed to the bug report.
> https://bugs.launchpad.net/bugs/1509097
>
> Title:
> Maas with http_proxy, Juju 1.24.6 -> 1.24.7, upgrade never finishes
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1509097/+subscriptions
>

--
David Britton <email address hidden>