Unable to add new Incus cluster members

Hi! I’ve recently upgraded my six node cluster to the latest version of Incus:

root@optiplex3050:~# dpkg -l | grep incus
ii incus 1:6.4-202408230437-debian12 amd64 Incus - Container and virtualization daemon
ii incus-base 1:6.4-202408230437-debian12 amd64 Incus - Container and virtualization daemon (container-only)
ii incus-client 1:6.4-202408230437-debian12 amd64 Incus - Command line client

Now, I want to add two new nodes to this existing cluster. I’m getting the same error messages on both of these nodes when I try to add them:

root@x79d8d:~# incus admin init
Would you like to use clustering? (yes/no) [default=no]: yes
What IP address or DNS name should be used to reach this server? [default=192.168.1.79]:
Are you joining an existing cluster? (yes/no) [default=no]: yes
Please provide join token: eyJzZXJ2Z…DI6MDAifQ==
All existing data is lost when joining a cluster, continue? (yes/no) [default=no] yes
Choose “source” property for storage pool “local”:
Would you like a YAML “init” preseed to be printed? (yes/no) [default=no]:
Error: Failed to join cluster: Failed request to add member: context deadline exceeded

Both of these new nodes are running Debian 12, and are new installs with the stable apt repo from zabbly. All nodes are running the same version of Incus. If I try to add a member again, I will get an error about local storage pool:

root@x79d8d:~# incus admin init
Would you like to use clustering? (yes/no) [default=no]: yes
What IP address or DNS name should be used to reach this server? [default=192.168.1.79]:
Are you joining an existing cluster? (yes/no) [default=no]: yes
Please provide join token: eyJzZXJ2Z…I6MDAifQ==
All existing data is lost when joining a cluster, continue? (yes/no) [default=no] yes
Choose “source” property for storage pool “local”: test
Would you like a YAML “init” preseed to be printed? (yes/no) [default=no]:
Error: Failed to join cluster: Failed to initialize member: Failed to initialize storage pools and networks: Failed to update storage pool “local”: Config key “source” is cluster member specific

I’d recommend running incus monitor --pretty on both the joining and the existing servers to try and get more details on what’s going on.