previously valid amazon environment now invalid?

[roger peppe]

I think this is a consequence of the pre-jenv-file fallback
code. Before .jenv files existed, all the information needed
to exist in the environments.yaml file, including
the control-bucket attribute. When we changed things
to store local state in a .jenv file, we also provided
a fallback to allow people to connect to their existing
bootstrapped environments with no .jenv file.

I suspect that's what you're seeing here - it's trying to fall
back to connecting to the environment specified in
your environments.yaml file, but that doesn't have all
the attributes available, so it fails accordingly.

That fallback code was designed to be around for only
a short time - I'd suggest removing it.

  cheers,
    rog.

On 27 April 2015 at 21:57, Nate Finch <nate.finch at canonical.com> wrote:
> If I do juju status with an unbootstrapped amazon environment, I get this:
>
> /home/nate/src/github.com/juju/juju master$ juju status
> ERROR Unable to connect to environment "amazon".
> Please check your credentials or use 'juju bootstrap' to create a new
> environment.
>
> Error details:
> invalid EC2 provider config: control-bucket: expected string, got nothing
>
> The error details seem to be incorrect.  control-bucket is not required (and
> in fact, I can bootstrap just fine with this configuration).
>
> Here's my config:
>
>   ## https://juju.ubuntu.com/docs/config-aws.html
>   amazon:
>     type: ec2
>     admin-secret: elided
>     # globally unique S3 bucket name
>     # control-bucket: juju-c2feecf0b1cd9ef0d4ea241dd90e10c3
>     # override if your workstation is running a different series to which
> you are deploying
>     default-series: trusty
>     agent-metadata-url: "http://juju-dist.s3.amazonaws.com/testing/tools"
>     enable-os-upgrade: false
>     logging-config: "<root>=DEBUG"
>     # bootstrap-timeout: 3600
>     # region defaults to us-east-1, override if required
>     # region: us-east-1
>     # Usually set via the env variable AWS_ACCESS_KEY_ID, but can be
> specified here
>
> I don't know when this changed, but something's wrong here.
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>