lxd update juju endpoint

[lucian]

hello,
i have juju and kubernetes installed with lxd on localhost.
after the install and restart my machine has a new local ip and
bootstrap-params endpoints are not reflecting that

from https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/412

[John A Meinel (jameinel)]

To get *you* connected back to the controlller, you should be able to look at ~/.local/share/juju/controllers.yaml which lists what IP address it thought the Controller was at, and you should be able to update that.

However, all of the agents on your localhost cloud are also going to be pointing at the old addresses, so you'll need to do something similar for each of the machines in /var/lib/juju/agents/*/agent.conf

I believe we have some work to automate updating agents, because backup + restore suffers from the same issue (you're usually restoring to a controller at a new IP address).
However, I'm not sure if the logic around updating all of the agents has been decoupled enough from 'restore' to allow you to easily invoke it directly. Needs some investigation.

[Andrew Wilkins (axwalk)]

I believe the problem is more nefarious than that. IIANM, the issue is that the cloud definition inside the controller refers to the old IP address (it's stored in the cloud endpoint). We need a way of updating the cloud definition inside the controller.

[John A Meinel (jameinel)]

Why would the controller IP be stored as information about the cloud? I
could see us storing the Host machine address so we can contact the correct
LXD agent, but likely that is just the .1 address and is unlikely to have
actually changed.

Is there another place we are storing the controller's IP address?

John
=:->

On Sep 15, 2017 09:50, "Andrew Wilkins" <email address hidden>
wrote:

> I believe the problem is more nefarious than that. IIANM, the issue is
> that the cloud definition inside the controller refers to the old IP
> address (it's stored in the cloud endpoint). We need a way of updating
> the cloud definition inside the controller.
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1716932
>
> Title:
> lxd update juju endpoint
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1716932/+subscriptions
>

[Andrew Wilkins (axwalk)]

:8443 is the LXD port. Juju is not connecting to the controller, it's connecting to LXD. The LXD host address is stored in the cloud endpoint.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.