Tom Parrott

@simondeziel do you see any more on these errors now? Thanks

Is this occurring when the instance is just starting/stopping/restarting?

Do you see the issue only when the instance isn't running?

And to be clear, the instances are in stopped or started state?

Agree with premise. But also worth noting the tokens only remain until lxd is restarted next, not indefinitely.

> We should be able to achieve this pretty easily with just an extra `tokens` DB table to hold them. > We'd effectively have LXD spawn Token type operations on...

Originally we didn't go that route because we wanted tokens to be back ported to 4.0 LTS without a schema change. But if we are introducing a schema change it...

I think this would make sense, but as well as the code change, will also need a DB patch to expand any previously stored non-member specific key into multiple values,...

Assuming LXD had the discussed SNAT feature... 1. LXD clusters require at least 3 members for HA (you can run a 2 member cluster but if one goes down the...

BTW, in the meantime you could just set `ipv4.nat=false` on the network and then add a manual MASQUERADE rule to each cluster member's firewall.