Migration tool duplicates Redis keys of node

Bug
1

I needed to correct a wrong value, my NS8 runs on Debian 12. It seems that reconnecting the migration tool in some cases (like wrong DNS settings) increases the last octet of the Wireguard VPN IP of the NS7 (10.5.4.10) but doesn’t adapt the “AllowedIPs” on NS8 correctly that still was set to 10.5.4.3.
Following steps helped:

Get the right Wireguard IP of NS7:

[root@testserver ~]# ip a s dev ns8
5: ns8: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000
    link/none
    inet 10.5.4.10/32 scope global ns8

Edit /etc/wireguard/wg0.conf on NS8 and change the AllowedIPs of the NS7 peer to the right one.

[Peer]
PublicKey = UjwxpNWsdRF/egLJDaJofb7fEYrUrH3pT3CxdS4Ws4o=
AllowedIPs = 10.5.4.10/32
Endpoint = 192.168.3.162:53080
PersistentKeepalive = 25

Restart wireguard service on NS8:

systemctl restart wg-quick@wg0

Here’s a similar issue, partly solved by changing the IP on NS7 to the allowed one on NS8 (other way round):

2 Likes
2

Bug filed here

1 Like
3

Fix released in core 2.8.2 and migration tool 1.0.13 :tada:

1 Like
4

I’ll give it a go later this evening. Thnx for the effort.

1 Like
5

After updating the migration tool on NS7 to 1.0.13 I retried the connection and this time this was successful. I was presented with a list of possible applications to migrate.
To try the tool I migrated Mattermost and this went flawlessly.
I updated DNS record to the new server and was able to log in Mattermost on the new NS8 instance.
I will open a new support ticket for the other applications since that migration is offtopic in this thread

2 Likes