juju switch -l does not return list of env names

re docs that's the inline cli docs for ref. ie juju switch -h

On Tue, Nov 12, 2013 at 10:05 AM, Curtis Hovey <email address hidden> wrote:

> ** Changed in: juju-core
> Status: New => Triaged
>
> ** Changed in: juju-core
> Importance: Undecided => High
>
> ** Changed in: juju-core
> Milestone: None => 1.17.0
>
> ** Tags added: docs switch ui
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1250285
>
> Title:
> juju switch -l does not return list of env names
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1250285/+subscriptions
>

I cannot reproduce this issue with tip. Could this be a co-install issue?

curtis@retrograde:~$ juju switch
Current environment: "local"
curtis@retrograde:~$ $GOPATH/bin/juju switch -l
Current environment: "local"

Environments:
 jujustack
 local
 public-tools-canonistack
 public-tools-hp
 test-aws
 test-azure
 test-can

try with a JUJU_HOME set (which i do because of encrypted home).

On Fri, Nov 15, 2013 at 10:27 AM, Curtis Hovey <email address hidden> wrote:

> I cannot reproduce this issue with tip. Could this be a co-install
> issue?
>
> curtis@retrograde:~$ juju switch
> Current environment: "local"
> curtis@retrograde:~$ $GOPATH/bin/juju switch -l
> Current environment: "local"
>
> Environments:
> jujustack
> local
> public-tools-canonistack
> public-tools-hp
> test-aws
> test-azure
> test-can
>
> ** Changed in: juju-core
> Status: Triaged => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1250285
>
> Title:
> juju switch -l does not return list of env names
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1250285/+subscriptions
>

JUJU_HOME is honoured for me using juju-core tip.

curtis@retrograde:~$ export JUJU_HOME=/home/curtis/Work/orangestack/
curtis@retrograde:~$ $GOPATH/bin/juju switch
Current environment: "staging"
curtis@retrograde:~$ $GOPATH/bin/juju switch -l
Current environment: "staging"

Environments:
 amazon
 azure
 hpcloud
 juju-gui-qa
 local
 maas
 orange
 staging
curtis@retrograde:~$ export JUJU_HOME=~/.juju
curtis@retrograde:~$ $GOPATH/bin/juju switch
Current environment: "local"
curtis@retrograde:~$ $GOPATH/bin/juju switch -l
Current environment: "local"

Environments:
 jujustack
 local
 public-tools-canonistack
 public-tools-hp
 test-aws
 test-azure
 test-canonistack
 test-hp

The problem triggers on JUJU_ENV being set.

kapil@realms-slice:~$ export JUJU_ENV=local
kapil@realms-slice:~$ juju switch -l
local
kapil@realms-slice:~$ unset JUJU_ENV
kapil@realms-slice:~$ juju switch -l
azure
canonistack
east
eu
hp
iaas-dev
iaas-stage
local
manual
openstack
public-cloud
southeast
training
west
kapil@realms-slice:~$