We are pulling he 2.3.6 agents

[Nicholas Skaggs]

All 2.3.6 binaries should now be removed from distribution. The snap 
should refresh to 2.3.5 if you have the 2.3.6 binary.

Thanks,

Nicholas

On 04/23/2018 10:06 AM, Adam Israel wrote:
> Hi all,
>
> What wasn't clear to me from the email is that, with 2.3.6 pulled, 
> we're unable to bootstrap new controllers without providing an 
> alternate agent-stream, i.e., --agent-stream=proposed.
>
> In future cases like this, is it feasible to roll back the snap to the 
> previous version, so new installs work as expected?
>
> On Sun, Apr 22, 2018 at 11:43 PM Tim Penhey <tim.penhey at canonical.com 
> <mailto:tim.penhey at canonical.com>> wrote:
>
>     Hey people,
>
>     We have field reports where a 2.3.6 upgrade interacted badly with some
>     charm settings causing Juju to get itself into a stuck, somewhat
>     corrupt
>     state. We are still evaluating how to fix this for stuck systems.
>
>     The symptom is the 2.3.6 upgrade fails and gets stuck.
>
>     The agents are being removed from streams to stop people accidentally
>     upgrading to a broken version, even though this breakage doesn't
>     impact
>     everyone.
>
>     We are also looking into the continuous integration tests around our
>     upgrades for extra testing to catch other issues like this one.
>
>     We will be releasing 2.3.7 shortly to address this isue.
>
>     Thanks for your patience.
>     Tim
>
>
>     -- 
>     Juju-dev mailing list
>     Juju-dev at lists.ubuntu.com <mailto:Juju-dev at lists.ubuntu.com>
>     Modify settings or unsubscribe at:
>     https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
> -- 
> Adam Israel, Software Engineer
> Canonical // Cloud DevOps // Juju // Ecosystem
>
>