On 7 May 2015 at 17:34, Curtis Hovey <email address hidden> wrote:
> Where did 1.22.1 come from. the Juju stable PPA before it was
> superseded? From Ubuntu trusty proposed?
>
Juju stable PPA (before it was superseded) we copy the package so that we
pin the version of Juju that we use.
> I cannot reproduce this case using both the certification tests and
> manually (6 separate attempts).
> A. When I bootstrap with juju 1.22.1 and deploy a stack. the agent
> versions are 1.22.1
>
B. If I ask for an upgrade, Juju correctly selects 1.23.2 (the current
> stable) and upgrades complete.
>
> Is an upgrade to 1.22.3 being explicitly requested?
> juju upgrade-juju --version=1.22.3
>
No, just bootstrap.
> Is the env using private streams that are missing the current stable?
>
No, just the default (streams.canonical.com ?), nothing pointing at
proposed or devel or the like.
On 7 May 2015 at 17:34, Curtis Hovey <email address hidden> wrote:
> Where did 1.22.1 come from. the Juju stable PPA before it was
> superseded? From Ubuntu trusty proposed?
>
Juju stable PPA (before it was superseded) we copy the package so that we
pin the version of Juju that we use.
> I cannot reproduce this case using both the certification tests and
> manually (6 separate attempts).
> A. When I bootstrap with juju 1.22.1 and deploy a stack. the agent
> versions are 1.22.1
>
B. If I ask for an upgrade, Juju correctly selects 1.23.2 (the current
> stable) and upgrades complete.
>
> Is an upgrade to 1.22.3 being explicitly requested?
> juju upgrade-juju --version=1.22.3
>
No, just bootstrap.
> Is the env using private streams that are missing the current stable?
>
No, just the default (streams. canonical. com ?), nothing pointing at
proposed or devel or the like.