When the GSLB Services or sites are referenced by Latitude and Longtitude coordinates in floating point in the GeoDB entry. This may lead to a scenario where an incorrect pool/site is chosen.
Avi Loadbalancer version 22.1.7, 30.2.2., 31.1.1 and below
The issue is caused due to a bug in the code with floating point round off calculations.
A server and client location can differ by up to 1 unit along the scaled longitude and scaled latitude used by Avi in calculating distance.
This issue happens only if there is a fraction involved.
If longitude and latitude are whole integer values this issue will not happen.
Workaround:
Edit the Geodb entries in the custom geodb file used to use whole integer values for the coordinates.
Bug ID: AV-232777
Fix Version: 30.2.3, 31.1.2, 22.1.7-2p6, 31.1.1-2p2