Comment 3 for bug 1927186

I believe this is probably a duplicate of the old local scheduler data issue and is not related to an active/active deployment.
This was discussed in the PTG.

This issue will happen even if you have a single cinder-volume as long as you have multiple cinder-scheduler services running. Moreover if you create a volume and then make N get-pools requests while there are no additional cinder requests (where N is the number of schedulers) you will most likely see that you don't get the same values.