Juju 2.3.7 has been released

[Chris Lee]

*Juju 2.3.7 has arrived. This is primarily a bug fix release. For the full
list of bugs, see  the 2.3.7 milestone.
This is a critical fix for a
bug (1765722 ) in one of the
upgrade steps in 2.3.6. We have pulled 2.3.6 from availability to avoid
people running into this problem.## Critical bugs fixed - 1765722
 Upgrading to 2.3.6 can fail with
"dotted field is not valid for ..."## Enhancements - 1764267
 Initial support for bootstrapping
a Juju controller on Bionic (support for new mongodb and changing of
available archive packages). You must specifically request a Bionic
controller with `--bootstrap-series=bionic`. The 2.3 series will always
default to using a Xenial image for 2.3 controllers.If you were affected by
any of the bugs fixed in this release
, your feedback is
appreciated. Please contact the Juju team using the communication channels
specified in the feedback section.## Get Juju.The easiest way to get Juju
is using the snap package. sudo snap install juju --classic## Feedback
Appreciated!We encourage everyone to let us know how you're using Juju.
Send us amessage on Twitter using #jujucharms, join us at #juju on freenode
IRC, andsubscribe to the mailing list at j...@lists.ubuntu.com
.## More informationTo learn more about Juju please
visit https://jujucharms.com .*
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: 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 > 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@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





--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: We are pulling he 2.3.6 agents

[Adam Israel]

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 
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@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
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev