Comment 12 for bug 1681853

So I think, 2.2-rc1 ends up producing agents that are in the 'proposed'
(devel?) stream, rather than the 'released' stream. I also believe that
official snaps of the juju client do not produce 'jujud' binaries inside
the snap, because there is an official jujud*.tar.gz that can be downloaded
from streams.canonical.com (--edge based releases do carry the jujud
binary, hence the 44MB vs 25MB).

However, controllers that are currently on 'stable' releases don't see
'proposed' streams as something they can target as an upgrade. It might be
possible to do something with "juju model-config -m controller
agent-stream=?", but its something I haven't personally tested.

Can you confirm whether you can/cannot bootstrap a new controller with the
2.1-rc1 snap?

John
=:->

On Tue, Jun 6, 2017 at 4:29 PM, Dmitrii Shcherbakov <
<email address hidden>> wrote:

> Well, now I cannot do anything at all.
>
> ubuntu@maas:~/juju/cmd$ snap info juju
> name: juju
> summary: "juju client"
> publisher: canonical
> contact: http://jujucharms.com
> description: |
> Through the use of charms, juju provides you with shareable, re-usable,
> and
> repeatable expressions of devops best practices.
> commands:
> - juju
> tracking: beta
> installed: 2.2-rc1 (1925) 25MB classic
> refreshed: 2017-06-05 21:52:07 -0400 EDT
> channels:
> latest/stable: 2.1.3 (1922) 24MB classic
> latest/candidate: 2.1.3 (1922) 24MB classic
> latest/beta: 2.2-rc1 (1925) 25MB classic
> latest/edge: 2.2-rc1+develop-7256fe0 (1915) 44MB classic
>
>
> ubuntu@maas:~/juju/cmd$ juju upgrade-juju -m controller
> no prepackaged tools available, using local agent binary 2.2-rc1.1
> ERROR no matching agent binaries available
>
> ubuntu@maas:~/juju/cmd$ juju upgrade-juju -m controller --agent-version
> 2.2-rc1
> ERROR no matching agent binaries available
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1681853
>
> Title:
> Juju Tools Upgrade from 2.0.2 to 2.1.2 fails: ERROR no matching tools
> available
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1681853/+subscriptions
>