| 2014-02-28 18:48:14 |
Curtis Hovey |
bug |
|
|
added bug |
| 2014-02-28 18:48:14 |
Curtis Hovey |
attachment added |
|
console output of the failed boostrap https://bugs.launchpad.net/bugs/1286279/+attachment/4001049/+files/trusty-boostrap-precise.log |
|
| 2014-02-28 19:20:45 |
Curtis Hovey |
description |
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. |
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 trsuty+1.17.3 -> precise+1.17.3
PASS trsuty+1.17.3 -> precise+1.17.4 |
|
| 2014-02-28 19:21:04 |
Curtis Hovey |
description |
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 trsuty+1.17.3 -> precise+1.17.3
PASS trsuty+1.17.3 -> precise+1.17.4 |
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 |
|
| 2014-02-28 19:22:08 |
Curtis Hovey |
description |
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 |
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 |
|
| 2014-02-28 19:27:37 |
Curtis Hovey |
description |
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 |
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
PASS precise+1.7.4 -> trusty+1.17.4 |
|
| 2014-02-28 19:32:33 |
Curtis Hovey |
description |
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
PASS precise+1.7.4 -> trusty+1.17.4 |
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
PASS precise+1.7.4 -> trusty+1.17.4
PASS win+1.7.4 -> precise+1.17.4 |
|
| 2014-02-28 19:32:58 |
Curtis Hovey |
description |
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
PASS precise+1.7.4 -> trusty+1.17.4
PASS win+1.7.4 -> precise+1.17.4 |
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 |
|
| 2014-02-28 19:38:56 |
Curtis Hovey |
description |
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 |
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 |
|
| 2014-02-28 19:39:42 |
Curtis Hovey |
description |
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 |
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 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 |
|
| 2014-02-28 21:20:01 |
Curtis Hovey |
summary |
juju 1.17.4 trusty client cannot bootstrap 1.17.x precise |
juju-mongodb breaks 1.17.4 trusty client bootstrap in CPC |
|
| 2014-02-28 21:24:39 |
Curtis Hovey |
description |
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 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 |
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
juju clients cannot if juju-mongodb is locally installed! juju-mongodb is installed by the juju-local package *only* if mongodb-server is not already installed. |
|
| 2014-02-28 21:24:50 |
Curtis Hovey |
tags |
precise trusty |
bootstrap mongodb precise trusty |
|
| 2014-02-28 21:34:26 |
Curtis Hovey |
tags |
bootstrap mongodb precise trusty |
bootstrap mongodb precise regression trusty |
|
| 2014-02-28 21:37:18 |
Curtis Hovey |
description |
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
juju clients cannot if juju-mongodb is locally installed! juju-mongodb is installed by the juju-local package *only* if mongodb-server is not already installed. |
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. |
|
| 2014-03-05 17:32:30 |
dann frazier |
bug |
|
|
added subscriber dann frazier |
| 2014-03-07 14:55:42 |
John A Meinel |
juju-core: assignee |
|
John A Meinel (jameinel) |
|
| 2014-03-07 15:52:50 |
John A Meinel |
juju-core: assignee |
John A Meinel (jameinel) |
Martin Packman (gz) |
|
| 2014-03-07 16:08:50 |
Launchpad Janitor |
branch linked |
|
lp:~gz/juju-core/revert_upstart_mongodb_1286279 |
|
| 2014-03-07 16:31:18 |
Martin Packman |
juju-core: status |
Triaged |
In Progress |
|
| 2014-03-08 17:59:18 |
Go Bot |
juju-core: status |
In Progress |
Fix Committed |
|
| 2014-03-14 15:51:34 |
Curtis Hovey |
juju-core: status |
Fix Committed |
Fix Released |
|
