juju list-controllers --format=yaml displays controller that cannot be addressed.

[Aaron Bentley]

As seen here:
http://reports.vapour.ws/releases/issue/5751c385749a56711194b317

[Tim Van Steenburgh (tvansteenburgh)]

What is the output of `juju list-controllers --format=yaml` in this environment?

What is juju 2.0-delta1?

Deployer doesn't impose any qualifications on the env name it is given. It simply passes it through to jujuclient, which attempts to connect to it.

[Aaron Bentley (abentley)]

list-controllers output was provided in the logs, e.g.
2016-06-03 15:06:31 INFO juju --debug list-controllers
2016-06-03 15:06:31 INFO juju.cmd supercommand.go:60 running juju [2.0-delta1 gc go1.6.1]
CONTROLLER MODEL USER CLOUD/REGION
local.aws-deployer-bundle* aws-deployer-bundle admin@local aws/ap-southeast-1

2016-06-03 15:06:31 INFO cmd supercommand.go:454 command finished

The environments were destroyed as part of test cleanup, so we can't re-run with --format=yaml.

Juju 2.0-delta1 was the version number used by the service-to-application branch, before it was merged. Now service-to-application has merged into master.

Before we removed the 'local.', it got further, although it did not complete. e.g.
http://reports.vapour.ws/releases/4027/job/aws-deployer-bundle/attempt/1720

[David Britton (dpb)]

Juju list-controller output is depended on by juju-deployer. It can't list a controller name that is not useable. From the output in comment #2, it apparently does in this in beta8, but will be fixed in beta9. Retargeting to juju-core.

[Cheryl Jennings (cherylj)]

Controllers bootstrapped with beta9 will show up in list-controllers without the 'local.' prefix.