lxd update juju endpoint
Bug #1716932 reported by
lucian
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
High
|
Unassigned |
Bug Description
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:/
To post a comment you must log in.
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.