Right I see. So setting manual chassis priorities is not possible at the moment in LXD.
In a LXD cluster all members are considered to be potential candidates to become leader, and so they are considered equal.
As such each OVN network will generate per-network random stable chassis IDs, with one of the cluster members being the preferred ingress/egress member.
The reason we generate this on a per OVN network basis is so that if you have multiple OVN networks, the same cluster member won’t be used as the primary for all networks, and instead the ingress/egress traffic will be roughly distributed across the cluster members.
It is expected that every cluster member be connected to the OVN network’s uplink network so they can potentially become the preferred ingress/egress member.
Perhaps you can open an issue over at https://github.com/lxc/lxd/issues where we can discuss the viability of your idea to have more manual control over these priorites.