Comment 4 for bug 1481557

DIMS,

This is our current Juno deployment. Using this for Kilo means that volumes can't be attached (as it seems to use a non-region specific keystone endpoint list to determine where the volume comes from.) In our case (2 regions), one will succeed in regression tests, and one will fail. The one that succeeds is random (based on endpoint id as near as I can tell). The one that fails has a higher endpoint id for cinder and fails as it selects the lower.

This works fine in Juno but fails in Kilo.

Poke "med_" in #openstack-nova IRC if you need more info (or update the bug).