Cannot bootstrap instances in ec2

[Tim Penhey]

On 02/04/13 18:39, David Cheney wrote:
> ubuntu at ip-10-130-181-131:~$ tail -f /var/log/juju/machine-1.log
> 2013/04/02 05:37:43 ERROR JUJU:jujud:machine jujud machine command
> failed: state entity name not found in configuration
> error: state entity name not found in configuration
> 2013/04/02 05:37:43 ERROR JUJU:jujud:machine jujud machine command
> failed: state entity name not found in configuration
> error: state entity name not found in configuration
> 2013/04/02 05:37:43 ERROR JUJU:jujud:machine jujud machine command
> failed: state entity name not found in configuration
> error: state entity name not found in configuration
> 2013/04/02 05:37:43 ERROR JUJU:jujud:machine jujud machine command
> failed: state entity name not found in configuration
> error: state entity name not found in configuration
> 2013/04/02 05:37:43 ERROR JUJU:jujud:machine jujud machine command
> failed: state entity name not found in configuration
> error: state entity name not found in configuration

OK... I think this may be fallout from earlier work that I did around
the series stuff, that is only impacting us now as we have made an
incompatible change to the configuration.

  juju boostrap --upload-tools

This (in trunk) creates tools for the version of the OS you are running
(i.e. quantal / raring), but when the tools are looked for, it is
looking for the default series for the environment (usually precise),
which then chooses incompatible tools from the public bucket, and BOOM
(well, not really boom).

My proposed solution is simple:

Don't use the series of the machine running juju to define the series
for version.Current:

Rietveld: https://codereview.appspot.com/8270045

Tim