Canonical Juju

  1. Bug #1555744
  2. Comment #2

Comment 2 for bug 1555744

Revision history for this message
Peter Matulis (petermatulis) wrote : Re: kill-controller prevents reuse of controller name

Tried again with same results. Maybe it's aws-specific.

$ dpkg-query -W juju2

juju2 2.0-beta2-0ubuntu1~16.04.1~juju1

$ juju kill-controller controller-aws3

$ juju bootstrap controller-aws4 aws

$ juju kill-controller controller-aws4

$ juju bootstrap --debug controller-aws4 aws

2016-03-14 15:46:06 INFO juju.cmd supercommand.go:59 running juju [2.0-beta2 gc go1.6]
2016-03-14 15:46:06 DEBUG juju.cmd.juju.commands bootstrap.go:355 preparing controller with config: map[type:ec2 name:controller-aws4]
2016-03-14 15:46:06 INFO juju.provider.ec2 provider.go:48 opening model "controller-aws4"
2016-03-14 15:46:06 DEBUG juju.environs.configstore disk.go:326 writing cache file
2016-03-14 15:46:06 ERROR cmd supercommand.go:448 cannot create controller "local.controller-aws4" info: model info already exists

Interestingly enough,

$ juju list-models

error: controller local.controller-aws4 not found

$ juju switch controller-gce

$ juju list-models

NAME OWNER LAST CONNECTION
controller-gce admin@local 2016-03-11

$ juju bootstrap controller-aws4 aws

ERROR cannot create controller "local.controller-aws4" info: model info already exists