incorrect instructions on failure when using --keep-broken

[Heather Lanigan]

Using juju bootstrap --keep-broken, when the bootstrap fails the INFO message tells the user to keep up the failed controller, however no controller exists:

2017-11-02 18:28:17 DEBUG juju.cmd.jujud main.go:187 jujud complete, code 0, err <nil>
14:28:17 INFO cmd bootstrap.go:504 bootstrap failed but --keep-broken was specified so resources are not being destroyed.
When you have finished diagnosing the problem, remember to clean up the failed controller.
See `juju kill-controller`.
ERROR failed to bootstrap model: subprocess encountered error code 1
14:28:17 DEBUG cmd supercommand.go:459 error stack:
subprocess encountered error code 1
github.com/juju/juju/cmd/juju/commands/bootstrap.go:601: failed to bootstrap model

$ juju controllers
ERROR No controllers registered.

Please either create a new controller using "juju bootstrap" or connect to
another controller that you have been given access to using "juju register".

-------------------------

Another question. How does the user know which resources to clean up? Instance, security groups, security rules...

[Ian Booth (wallyworld)]

keep broken is more of an admin tool rather than an end user tool.
If bootstrap fails, there won't be any controller registered - you need to ssh in to the machine via its IP address. You typically need to use the cloud console (or equivalent CLI tool) to destroy the machine and its resources.

[Anastasia (anastasia-macmood)]

PR agaisnt develop: https://github.com/juju/juju/pull/8030