Reconnecting a controller

[Andrew McDermott]

I'm wondering whether the agent failed to start after you resumed it from
the console.

You can find the original IP address by looking in:

  $HOME/.local/share/jujucontrollers.yaml

For example, I bootstrapped on AWS and found the instance IP address via:

$ grep -A 5 aws ~/.local/share/juju/controllers.yaml
aws-eu-west-1:
  unresolved-api-endpoints: ['52.48.55.22:17070', '172.31.31.222:17070']
  uuid: a3518118-322e-4423-845d-fddee0059353
  api-endpoints: ['52.48.55.22:17070', '172.31.31.222:17070']

Given that information you can try and ssh to the instance:

$ ssh -i ~/.local/share/juju/ssh/juju_id_rsa ubuntu at 52.48.55.22
(which worked in my case)

If that doesn't work you man find the IP address has changed and, if so,
you would have to use the AWS console to find its new IP address and update
the existing entries in the controllers.yaml.

HTH
Andy

On 9 December 2016 at 09:36, Stefano Simonelli <stefano at scaledb.com> wrote:

> Hi you all,
> is it possible to reconnect a controller to its VM ?
>
> I have done this :
>
> - I created a controller in my local VBOX using AWS as a target :
> juju bootstrap aws/us-east-1 ctrl_aws_us-east-3
> - I stopped / started the AWS vm using the AWS functionalities
> - at this poit, I was no more able to use :
> - juju status
> - neither to destroy the controller, using :
> juju destroy-controller ctrl_aws_us-east-3  --destroy-all-models -y
>
> thanks for helping.
>
> --
> Stefano Simonelli
> ScaleDB, Inc.
> Mobile: +39 335/545.71.51
>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
>


-- 
Andrew McDermott <andrew.mcdermott at canonical.com>
Juju Core Sapphire team <http://juju.ubuntu.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20161209/5fdca5de/attachment.html>