Juju 2.3-rc2 is here!
merlijn.sebrechts at gmail.com
Fri Dec 8 09:43:37 UTC 2017
2017-12-07 13:33 GMT+01:00 Mark Shuttleworth <mark at ubuntu.com>:
> On 12/06/2017 02:51 PM, Nicholas Skaggs wrote:
> > 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
> > 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.
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..
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Juju