`juju environments` fails due to missing ~/.juju/current-environment

[Adam Israel]

Summary:

The Juju Environment System (JES) does not work on a fresh install due to lack of ~/.juju/current-environment

Setup:

juju 1.25-beta1
ubuntu trusty
fresh vm

Details:

I launched a new Vagrant VM, installed juju 1.25-beta1 via PPA, and ran apt-get update && apt-get upgrade. I set the "jes" feature flag, destroyed the local environment, and bootstrapped. Then I attempted to create a new environment:

$ juju system create-environment test
error: no system specified

$ ls ~/.juju/
environments environments.yaml jclient local ssh

$ juju switch local
-> local

$ ls ~/.juju/
current-environment environments environments.yaml jclient local ssh

$ juju system create-environment test
created environment "test"
local -> test

This can be recreated by deleting ~/.juju/current-environment and re-running the juju system commands.

[Jesse Meek (waigani)]

fix: http://reviews.vapour.ws/r/3256

[Cheryl Jennings (cherylj)]

Looks like this was fixed in master in this PR: https://github.com/juju/juju/pull/3883