Gregory Thiemonge 4b87554b59 Fix potential race conditions on update requests in the v2 worker ... The v2 worker was not waiting for a resource to be set to PENDING_UPDATE before updating it effectively. In some circumstances (loaded server/slow DB for instance), the resources may have been updated with old data from the DB, resulting in a no-op update. This wait for a PENDING_UPDATE state exists in amphorav1 but it was not moved to v2 when we switched the logic from the DB-based objects to dict-based objects. Note for stable/xena: this backport also contains [0] which improves code coverage. [0] I403e1861b1b51c07edad35c64ffac22167342c88 Story 2009887 Task 44645 Story 2009985 Task 45032 Change-Id: I433e074c2eac5f6875ee5dace8faf86969b24f66 (cherry picked from commit 6042de759d) (cherry picked from commit c31051b388)		2022-06-24 11:41:22 +02:00
..
flows	Fix LB set in ERROR too early in the revert flow	2021-11-16 14:45:51 +01:00
tasks	Restart rsyslog from cloud-init	2022-04-12 12:49:27 +02:00
__init__.py	Create Amphora V2 provider driver	2019-06-05 14:30:29 -07:00
test_controller_worker.py	Fix potential race conditions on update requests in the v2 worker	2022-06-24 11:41:22 +02:00