When listing records in the V1 API, two calls to central
are made - once for records once for recordsets - if the
content of either changes between the two calls, a failure
can occour. Instead, we already have all the data we need
so use it from the recordsets rather than make two calls
Change-Id: Ic43d7e8c0d60267ec4788b63ed5f7e88e7bbe625
Closes-Bug: 1487934
(cherry picked from commit eea5c1e8ad55d7ec17bf4695ba63efbc0e170784)
Reviewed: https:/ /review. openstack. org/227433 /git.openstack. org/cgit/ openstack/ designate/ commit/ ?id=21de1d53515 82bf1854ecf2e9b 7d6e09e5819248
Committed: https:/
Submitter: Jenkins
Branch: stable/kilo
commit 21de1d5351582bf 1854ecf2e9b7d6e 09e5819248
Author: Kiall Mac Innes <email address hidden>
Date: Tue Sep 22 14:05:01 2015 +0100
Fix race condition in V1 Records API
When listing records in the V1 API, two calls to central
are made - once for records once for recordsets - if the
content of either changes between the two calls, a failure
can occour. Instead, we already have all the data we need
so use it from the recordsets rather than make two calls
Change-Id: Ic43d7e8c0d6026 7ec4788b63ed5f7 e88e7bbe625 c17bf4695ba63ef bc0e170784)
Closes-Bug: 1487934
(cherry picked from commit eea5c1e8ad55d7e