Comment 0 for bug 1286279
Revision history for this message
| Curtis Hovey (sinzui) wrote juju 1.17.4 trusty client cannot bootstrap 1.17.x precise | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
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.