garage status
keeps displaying old IP for itself #761
Labels
No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#761
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hello,
I have changed the network addressing of all the nodes in my setup, from
10.3.x.x/24
to10.66.x.x/24
.All
*_bind_addr
,*_public_addr
andbootstrap_peers
were updated and nodes restarted. There is not a single reference to10.3.x.x
remaining in any node'sgarage.toml
.The network interface that was assigned the
10.3.x.x
address was removed from the system.Everything works correctly (all nodes are interconnected and work flawlessly), however,
garage status
on each nodes keeps displaying the old10.3.x.x
address for itself, while correctly displaying the new10.66.x.x
address for the other nodes.On the other hand
garage node id
correctly displays its new10.66.x.x
address.Same occurs with
garage status
on all other nodes: remote node addresses are displayed correctly, while the node itself lists its own, old,10.3.x.x
address.While this seems to be a very minor issue, i'd like to fix it.
I couldn't find anything related to this issue in the documentation nor here in the gitea issues.
Any ideas on how to fix this?
Thanks,
Hello, sorry for not answering this earlier.
Does the issue persist after restarting the Garage daemons?
I'm not sure exactly where the issue comes from, but you should check here:
garage status
: https://git.deuxfleurs.fr/Deuxfleurs/garage/src/branch/main/src/rpc/system.rsIf the issue disappears after restating the nodes, I think it's most likely due to how the peering manager learns the IP for the local node. I think it learns it once, from remote nodes (or from the config file), and doesn't ever change it after, unless the daemon is restarted.
Hello,
Actually, it seems to disappear after the node has been running for some time (ie. all nodes are displayed with up-to-date addresses), then returns after a node restart, and disappears again after a while (couldn't say for sure, but it lingers with old IP for around a day).
@vk, I would be interested if you could check if the undesirable behavior disappears in v1.0.0. In theory it should be fixed.