Comment 1 for bug 1204388

This isn't all upside, I think. We're going to end up with extraneous error messages. Is this acceptable?

No juju environment configuration file exists.
Please create a configuration by running:
    juju init -w
then edit the file to configure your juju environment.
You can then re-run bootstrap.
2013-07-24 08:17:28 ERROR juju supercommand.go:235 command failed: open /tmp/juju_home/environments.yaml: no such file or directory
error: open /tmp/juju_home/environments.yaml: no such file or directory