The release of 1.17.4 was aborted because my 1.17.4 trusty client could not bootstrap a 1.17.4 precise state-server on aws, hp, or azure. All timed out at "Bootstrapping Juju machine agent". The stream metadata was revert and the bootstrap test was perform with a 1.17.4 trusty client and a 1.17.3 precise state-server...it failed the same way.
While the juju packages never sent public, Ubuntu had already started building them for trusty. This issue needs a quick fix, or we release 1.17.3 as 1.17.5 to revert the damage.
Juju CI tests precise clients deploying to trusty, not the inverse, and it uses mongodb-server
Tested combinations of amd64 bootstraps of series+version *with* juju-mongodb installed
PASS trusty+1.16.6 -> precise+1.16.6
PASS trusty+1.17.3 -> precise+1.17.3
PASS trusty+1.17.3 -> precise+1.17.4
FAIL trusty+1.17.4 -> precise+1.17.4
FAIL trusty+1.17.4 -> precise+1.17.3
FAIL trusty+1.17.4 -> trusty+1.17.4
PASS precise+1.7.4 -> trusty+1.17.4
PASS win+1.7.4 -> precise+1.17.4
Tested after juju-mongodb *removed*
PASS trusty+1.17.4 -> precise+1.17.4
PASS trusty+1.17.4 -> precise+1.17.3
PASS trusty+1.17.4 -> precise+1.17.4
juju clients cannot bootstrap in the public clouds when juju-mongodb is locally installed! juju-mongodb is installed by the juju-local package *only* if mongodb-server is not already installed. This affects new installs and users who want to try the new package.
Is this considered fixed in 1.17.5 because we reverted the mongodb probe?
It means local won't work on Trusty with just juju-mongodb, but we can get
there in the next release. (We need to change it so the "juju" client
doesn't probe, the "jujud" server does.)
John
=:->
On Feb 28, 2014 11:45 PM, "Curtis Hovey" <email address hidden> wrote:
> ** Description changed:
>
> The release of 1.17.4 was aborted because my 1.17.4 trusty client could
> not bootstrap a 1.17.4 precise state-server on aws, hp, or azure. All
> timed out at "Bootstrapping Juju machine agent". The stream metadata was
> revert and the bootstrap test was perform with a 1.17.4 trusty client
> and a 1.17.3 precise state-server...it failed the same way.
>
> While the juju packages never sent public, Ubuntu had already started
> building them for trusty. This issue needs a quick fix, or we release
> 1.17.3 as 1.17.5 to revert the damage.
>
> Juju CI tests precise clients deploying to trusty, not the inverse.
>
> Tested combinations
> PASS trusty+1.16.6 -> precise+1.16.6
> PASS trusty+1.17.3 -> precise+1.17.3
> PASS trusty+1.17.3 -> precise+1.17.4
> +
> FAIL trusty+1.17.4 -> precise+1.17.4
> FAIL trusty+1.17.4 -> precise+1.17.3
> FAIL trusty+1.17.4 -> trusty+1.17.4
>
> PASS precise+1.7.4 -> trusty+1.17.4
> PASS win+1.7.4 -> precise+1.17.4
>
> ** Description changed:
>
> The release of 1.17.4 was aborted because my 1.17.4 trusty client could
> not bootstrap a 1.17.4 precise state-server on aws, hp, or azure. All
> timed out at "Bootstrapping Juju machine agent". The stream metadata was
> revert and the bootstrap test was perform with a 1.17.4 trusty client
> and a 1.17.3 precise state-server...it failed the same way.
>
> While the juju packages never sent public, Ubuntu had already started
> building them for trusty. This issue needs a quick fix, or we release
> 1.17.3 as 1.17.5 to revert the damage.
>
> Juju CI tests precise clients deploying to trusty, not the inverse.
>
> - Tested combinations
> + Tested combinations of amd64 bootstraps of series+version
> PASS trusty+1.16.6 -> precise+1.16.6
> PASS trusty+1.17.3 -> precise+1.17.3
> PASS trusty+1.17.3 -> precise+1.17.4
>
> FAIL trusty+1.17.4 -> precise+1.17.4
> FAIL trusty+1.17.4 -> precise+1.17.3
> FAIL trusty+1.17.4 -> trusty+1.17.4
>
> PASS precise+1.7.4 -> trusty+1.17.4
> PASS win+1.7.4 -> precise+1.17.4
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> https:/
>
> Title:
> juju 1.17.4 trusty client cannot bootstrap 1.17.x precise
>
> To manage notifications about this bug go to:
> https:/
>