22eb2e2538
When updating a resource that hasn't changed, we didn't previously retry the write when the atomic_key of the resource didn't match what we expect. In addition to locking a resource to update it, the atomic key is also incremented when modifying metadata and storing cached attribute values. Apparently there is some mechanism that can cause this to happen in the time between when the resource is loaded and when we attempt to update the template ID &c. in the DB. When the resource is not locked and its template ID hasn't changed since we loaded it, we can assume that the update failed due to a mismatched atomic key alone. Handle this case by sending another resource-check RPC message, so that the operation check will be retried with fresh data from the DB. Change-Id: I5afd5602096be54af5da256927fe828366dbd63b Closes-Bug: #1763021 |
||
---|---|---|
.. | ||
service | ||
__init__.py | ||
test_check_resource.py | ||
test_dependencies.py | ||
test_engine_worker.py | ||
test_node_data.py | ||
test_plugin_manager.py | ||
test_resource_type.py | ||
test_scheduler.py | ||
test_sync_point.py | ||
tools.py |