[BUG] duplicate connection based on name as well as UUID

Hey all -- I was connecting a gateway cloned using gwcmd, but that had a new UUID (i deleted the .uuid and restarted the gateway as well as manually confirming the UUID) and still got a duplicate connection error on the gateway network til I changed the gateway's name. The stack trace also explicitly called out the name of the gateway. The docs say UUID is all that matters though.

Docs are wrong, because only the gateway name is used to tell gateways apart when messaging or making remote connections.

1 Like

@ ignition team, the relevant incorrect paragraph is here:
"If you are cloning Gateways to then be connected via Gateway Network, it is important to notice that there is a Gateway unique identifier in %IgnitionInstallationDirectory%/data/.uuid. No two Gateways connected via Gateway Network should share a .uuid. Generally, Gateways are cloned by restoring the same Gateway backup on multiple servers. Since Gateway backups carry their .uuid with them, restoring the same Gateway on multiple servers will result in multiple Gateways having the same .uuid. To get around this, you must stop your Ignition service, delete %IgnitionInstallationDirectory%/data/.uuid, then start your Ignition service so that a new, unique .uuid is generated. Doing this before connecting two cloned Gateways will prevent any .uuid collisions."

on Gateway Network | Ignition User Manual

That doesn't actually say you don't have to change the gateway name, too. :man_shrugging:

2 Likes

ok technically you're right, but it does seem to have a pretty clear implication that that's all you need to worry about