Comment 5 for bug 1172973

A log of my session, fwiw

ubuntu@maas-dev:~/.juju$ juju status
error: file 'provider-state' not found not found
ubuntu@maas-dev:~/.juju$ juju bootstrap
2013-06-06 00:15:37 DEBUG juju environprovider.go:24 environs/maas: opening environment "maas".
2013-06-06 00:15:38 DEBUG juju environ.go:94 environs/maas: bootstrapping environment "maas"
2013-06-06 00:15:38 INFO juju tools.go:25 environs: reading tools with major version 1
2013-06-06 00:15:38 DEBUG juju storage.go:49 environs/tools: reading v1.* tools
2013-06-06 00:15:38 INFO juju tools.go:29 environs: falling back to public bucket
2013-06-06 00:15:38 DEBUG juju storage.go:49 environs/tools: reading v1.* tools
2013-06-06 00:15:38 ERROR juju supercommand.go:234 command failed: no tools available
error: no tools available
ubuntu@maas-dev:~/.juju$ env | grep AWS
ubuntu@maas-dev:~/.juju$ juju sync-tools --debug
error: environment has no access-key or secret-key
ubuntu@maas-dev:~/.juju$ juju sync-tools --debug
2013-06-06 00:16:57 INFO juju ec2.go:132 environs/ec2: opening environment "juju-public"
2013-06-06 00:16:57 ERROR juju synctools.go:115 failed to initialize the official bucket environment
2013-06-06 00:16:57 ERROR juju supercommand.go:234 command failed: environment has no access-key or secret-key
error: environment has no access-key or secret-key
ubuntu@maas-dev:~/.juju$ cat environments.yaml
default: maas
environments:
  maas:
    type: maas
    # Change this to where your MAAS server lives. It must specify the base path.
    maas-server: 'http://10.0.3.83/MAAS/'
    maas-oauth: 'kmtLZj6UmgN3TLPpgJ:79r2Hjts2L42ntdJwE:5FK4FQB2J9yF5ZcWSpCR9hMyedPVLtUQ'
    admin-secret: d0e51b71cebd919c36f4f5f3bad1432d
    default-series: precise
    authorized-keys-path: ~/.ssh/authorized_keys # or any file you want.