Excerpts from Andrew Glen-Young's message of Mon Oct 31 17:02:54 UTC 2011:
> Public bug reported:
> I have started experimenting with juju using an Openstack installation.
> When running 'juju bootstrap' I receive a fatal error message that the
> AMI could not be found:
> Error Message: Image ami-a7f539ce could not be found.
> I have overridden the default-ami in my ~/.juju/environments.yaml file.
> It looks like juju is not using the default-ami configuration settings
> correctly. I expect to be override the default ami that juju uses for
> the bootstrap node since the 'ami-a7f539ce' does not exist on the
> Openstack installation.
> ---- Configuration and example ----
> Juju version:
> juju 0.5+bzr411-1juju1~oneiric1
> Juju environments file (~/.juju/environments.yaml):
> # Some of this has been redacted.
> type: ec2
> control-bucket: juju-7af9961c0e0746e4b619XXXXXXXXXXXX
> admin-secret: 50dd078c467f42878a7dXXXXXXXXXXXX
> default-series: oneiric
> access-key: c211d568-1c10-4cd4-a975-80af38342b41:agy_project
> secret-key: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
> s3-uri: http://172.16.93.65:3333
> ec2-uri: http://172.16.93.65:8773/services/Cloud
> default-instance-type: m1.tiny
> default-ami: ami-00000002
Hi Andrew! The appropriate setting is default-image-id.
This is actually then a duplicate of bug #824787