Juju 2.3-rc2 is here!

[Nicholas Skaggs]

A new release of Juju is here, 2.3-rc2. This is primarily a bug fix release
which addresses issues carried over from rc1.

## New and Improved

* juju list-models is significantly faster, especially on controllers with
large numbers of models

* juju no longer records the execution of the update-status hook. This
means that you will no longer see 'idle' units move to 'executing' showing
'running update-status hook'. This also means that it isn't recorded in the
show-status-log for the unit. As a related item, the squashing of the
status-log, which was buggy, has been removed.

## Fixes

For a list of all bugs fixed in this release, see

https://launchpad.net/juju/+milestone/2.3-rc2


## How can I get it?

The best way to get your hands on this release of Juju is to install it as
a snap package (see https://snapcraft.io/ for more info on snaps).

snap install juju --classic --candidate

Other packages are available for a variety of platforms. Please see the
online documentation at https://jujucharms.com/docs/stable/reference-install.
Those subscribed to a snap channel should be automatically upgraded. If
you’re using the ppa/homebrew, you should see an upgrade available.

## Feedback Appreciated!

We encourage everyone to let us know how you're using Juju. Send us a

message on Twitter using #jujucharms, join us at #juju on freenode, and

subscribe to the mailing list at ***@lists.ubuntu.com.

## More information
To learn more about juju please visit https://jujucharms.com.

[Merlijn Sebrechts]

Is there a way to upgrade a controller from rc1.1 to rc2?

Post by Nicholas Skaggs
A new release of Juju is here, 2.3-rc2. This is primarily a bug fix
release which addresses issues carried over from rc1.
## New and Improved
* juju list-models is significantly faster, especially on controllers with
large numbers of models
* juju no longer records the execution of the update-status hook. This
means that you will no longer see 'idle' units move to 'executing' showing
'running update-status hook'. This also means that it isn't recorded in the
show-status-log for the unit. As a related item, the squashing of the
status-log, which was buggy, has been removed.
## Fixes
For a list of all bugs fixed in this release, see
https://launchpad.net/juju/+milestone/2.3-rc2
## How can I get it?
The best way to get your hands on this release of Juju is to install it as
a snap package (see https://snapcraft.io/ for more info on snaps).
snap install juju --classic --candidate
Other packages are available for a variety of platforms. Please see the
online documentation at https://jujucharms.com/docs/
stable/reference-install. Those subscribed to a snap channel should be
automatically upgraded. If you’re using the ppa/homebrew, you should see an
upgrade available.
## Feedback Appreciated!
We encourage everyone to let us know how you're using Juju. Send us a
message on Twitter using #jujucharms, join us at #juju on freenode, and
## More information
To learn more about juju please visit https://jujucharms.com.
--
Juju-dev mailing list
Modify settings or unsubscribe at: https://lists.ubuntu.com/
mailman/listinfo/juju-dev

[Tim Penhey]

Hi Merlijn,

You should be able to go:
juju upgrade-juju -m controller

That should do the trick. If the client version is different you may
want to specify the agent version:

juju upgrade-juju -m controller --agent-version 2.3-rc2

Tim

Post by Merlijn Sebrechts
Is there a way to upgrade a controller from rc1.1 to rc2?
A new release of Juju is here, 2.3-rc2. This is primarily a bug fix
release which addresses issues carried over from rc1.
## New and Improved
* juju list-models is significantly faster, especially on
controllers with large numbers of models
* juju no longer records the execution of the update-status hook.
This means that you will no longer see 'idle' units move to
'executing' showing 'running update-status hook'. This also means
that it isn't recorded in the show-status-log for the unit. As a
related item, the squashing of the status-log, which was buggy, has
been removed.
## Fixes
For a list of all bugs fixed in this release, see
https://launchpad.net/juju/+milestone/2.3-rc2
<https://launchpad.net/juju/+milestone/2.3-rc2>
## How can I get it?
The best way to get your hands on this release of Juju is to install
it as a snap package (see https://snapcraft.io/for more info on snaps).
        snap install juju --classic --candidate
Other packages are available for a variety of platforms. Please see
the online documentation at
https://jujucharms.com/docs/stable/reference-install
<https://jujucharms.com/docs/stable/reference-install>. Those
subscribed to a snap channel should be automatically upgraded. If
you’re using the ppa/homebrew, you should see an upgrade available.
## Feedback Appreciated!
We encourage everyone to let us know how you're using Juju. Send us a
message on Twitter using #jujucharms, join us at #juju on freenode, and
## More information
To learn more about juju please visit https://jujucharms.com.
--
Juju-dev mailing list
https://lists.ubuntu.com/mailman/listinfo/juju-dev
<https://lists.ubuntu.com/mailman/listinfo/juju-dev>

[Merlijn Sebrechts]

I tried this but I get the error that no agent binaries are found? I can
send you the exact error tomorrow, I don't have my laptop with me at the
moment.

Post by Tim Penhey
Hi Merlijn,
juju upgrade-juju -m controller
That should do the trick. If the client version is different you may
juju upgrade-juju -m controller --agent-version 2.3-rc2
Tim

Post by Merlijn Sebrechts
Is there a way to upgrade a controller from rc1.1 to rc2?
A new release of Juju is here, 2.3-rc2. This is primarily a bug fix
release which addresses issues carried over from rc1.
## New and Improved
* juju list-models is significantly faster, especially on
controllers with large numbers of models
* juju no longer records the execution of the update-status hook.
This means that you will no longer see 'idle' units move to
'executing' showing 'running update-status hook'. This also means
that it isn't recorded in the show-status-log for the unit. As a
related item, the squashing of the status-log, which was buggy, has
been removed.
## Fixes
For a list of all bugs fixed in this release, see
https://launchpad.net/juju/+milestone/2.3-rc2
<https://launchpad.net/juju/+milestone/2.3-rc2>
## How can I get it?
The best way to get your hands on this release of Juju is to install
it as a snap package (see https://snapcraft.io/for more info on

snaps).

Post by Merlijn Sebrechts
snap install juju --classic --candidate
Other packages are available for a variety of platforms. Please see
the online documentation at
https://jujucharms.com/docs/stable/reference-install
<https://jujucharms.com/docs/stable/reference-install>. Those
subscribed to a snap channel should be automatically upgraded. If
you’re using the ppa/homebrew, you should see an upgrade available.
## Feedback Appreciated!
We encourage everyone to let us know how you're using Juju. Send us a
message on Twitter using #jujucharms, join us at #juju on freenode,

and

Post by Merlijn Sebrechts
## More information
To learn more about juju please visit https://jujucharms.com.
--
Juju-dev mailing list
https://lists.ubuntu.com/mailman/listinfo/juju-dev
<https://lists.ubuntu.com/mailman/listinfo/juju-dev>

[Nicholas Skaggs]

Is your agent stream set to released per chance?

juju model-config -m controller

If so, your client won't see the agent binaries as they aren't in the
release stream (2.3 isn't yet released).

Nicholas

Post by Merlijn Sebrechts
I tried this but I get the error that no agent binaries are found? I
can send you the exact error tomorrow, I don't have my laptop with me
at the moment.
Hi Merlijn,
  juju upgrade-juju -m controller
That should do the trick. If the client version is different you may
  juju upgrade-juju -m controller --agent-version 2.3-rc2
Tim

Post by Merlijn Sebrechts
Is there a way to upgrade a controller from rc1.1 to rc2?
2017-11-29 1:03 GMT+01:00 Nicholas Skaggs
     A new release of Juju is here, 2.3-rc2. This is primarily a

bug fix

Post by Merlijn Sebrechts
     release which addresses issues carried over from rc1.
     ## New and Improved
     * juju list-models is significantly faster, especially on
     controllers with large numbers of models
     * juju no longer records the execution of the update-status

hook.

Post by Merlijn Sebrechts
     This means that you will no longer see 'idle' units move to
     'executing' showing 'running update-status hook'. This also

means

Post by Merlijn Sebrechts
     that it isn't recorded in the show-status-log for the unit. As a
     related item, the squashing of the status-log, which was

buggy, has

Post by Merlijn Sebrechts
     been removed.
     ## Fixes
     For a list of all bugs fixed in this release, see
https://launchpad.net/juju/+milestone/2.3-rc2

<https://launchpad.net/juju/+milestone/2.3-rc2>

Post by Merlijn Sebrechts
     <https://launchpad.net/juju/+milestone/2.3-rc2

<https://launchpad.net/juju/+milestone/2.3-rc2>>

Post by Merlijn Sebrechts
     ## How can I get it?
     The best way to get your hands on this release of Juju is to

install

Post by Merlijn Sebrechts
     it as a snap package (see https://snapcraft.io/for more info

on snaps).

Post by Merlijn Sebrechts
             snap install juju --classic --candidate
     Other packages are available for a variety of platforms.

Please see

Post by Merlijn Sebrechts
     the online documentation at
https://jujucharms.com/docs/stable/reference-install

<https://jujucharms.com/docs/stable/reference-install>

Post by Merlijn Sebrechts
     <https://jujucharms.com/docs/stable/reference-install

<https://jujucharms.com/docs/stable/reference-install>>. Those

Post by Merlijn Sebrechts
     subscribed to a snap channel should be automatically

upgraded. If

Post by Merlijn Sebrechts
     you’re using the ppa/homebrew, you should see an upgrade

available.

Post by Merlijn Sebrechts
     ## Feedback Appreciated!
     We encourage everyone to let us know how you're using Juju.

Send us a

Post by Merlijn Sebrechts
     message on Twitter using #jujucharms, join us at #juju on

freenode, and

Post by Merlijn Sebrechts
     ## More information
     To learn more about juju please visit https://jujucharms.com.
     --
     Juju-dev mailing list
https://lists.ubuntu.com/mailman/listinfo/juju-dev

<https://lists.ubuntu.com/mailman/listinfo/juju-dev>

Post by Merlijn Sebrechts
     <https://lists.ubuntu.com/mailman/listinfo/juju-dev

<https://lists.ubuntu.com/mailman/listinfo/juju-dev>>

[Mark Shuttleworth]

Post by Nicholas Skaggs
Is your agent stream set to released per chance?
juju model-config -m controller
If so, your client won't see the agent binaries as they aren't in the
release stream (2.3 isn't yet released).

I wonder if we can be more user friendly about this.

For example, if we had ONE stream, but the releases were tagged, then in
this case we could find it, and give a more helpful message like:

  juju upgrade-juju -m controller
  Version 2.3-rc2 exists but is tagged 'candidate', please use explicit
--agent-version to proceed

  juju upgrade-juju -m controller --agent-version 2.3-rc2
  Downloading juju 2.3-rc2.....

Does that make sense? Everyone can see the candidate releases, but they
only get them automatically if they have said they want them.
Nevertheless it's easy for them to see that the candidate release exists
and how to get it.

Mark

[Merlijn Sebrechts]

Post by Mark Shuttleworth

Post by Nicholas Skaggs
Is your agent stream set to released per chance?

Yes it is. This is weird, why doesn't the controller just take the
agent-stream that it was bootstrapped with?


Attribute From Value
agent-metadata-url default ""
agent-stream default released
agent-version model 2.3-rc1.1

Post by Mark Shuttleworth

Post by Nicholas Skaggs
juju model-config -m controller
If so, your client won't see the agent binaries as they aren't in the
release stream (2.3 isn't yet released).

I wonder if we can be more user friendly about this.
For example, if we had ONE stream, but the releases were tagged, then in
juju upgrade-juju -m controller
Version 2.3-rc2 exists but is tagged 'candidate', please use explicit
--agent-version to proceed
juju upgrade-juju -m controller --agent-version 2.3-rc2
Downloading juju 2.3-rc2.....
Does that make sense? Everyone can see the candidate releases, but they
only get them automatically if they have said they want them.
Nevertheless it's easy for them to see that the candidate release exists
and how to get it.

My knowledge of how these streams work is limited but I actually just
expect the agent stream to be the same as the snap channel by default. This
seems to be the case for bootstrapping: when you install the candidate snap
and bootstrap a controller, the controller is the same version as the snap.
So naturally, I expect `juju upgrade-juju` to upgrade the controller to the
latest beta release.

Using snap channels to select which release you want is very ease and
common. Every "new dev release" email from the Juju team explains how to
install the dev release using snap channels..

Post by Mark Shuttleworth
Mark