[MESOS-9010] `UPDATE_STATE` can race with `UPDATE_OPERATION_STATUS` for a resource provider.

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 1.7.0
• Component/s: storage
• Labels: mesosphere storage
• Target Version/s: 1.7.0
• Epic Link: Resource Provider and CSI Tech Debt
• Sprint: Mesosphere Sprint 2018-22, Mesosphere Sprint 2018-23, Mesosphere Sprint 2018-24
• Story Points: 2
• Assignee: Chun-Hung Hsiao
• Reporter: Chun-Hung Hsiao
• Shepherd: Benjamin Bannier
• Created: 20/Jun/18 03:09
• Updated: 13/Jul/18 21:47
• Resolved: 13/Jul/18 21:47

Description

Since a resource provider and its operation status update manager run in different actors, for a completed operation, its `UPDATE_OPERATION_STATUS` call may race with an `UPDATE_STATE`. When the `UPDATE_STATE` arrives to the agent earlier, the total resources will be updated, but the terminal status of the completed operation will be ignored since it is known by both the agent and the resource provider. As a result, when the `UPDATE_OPERATION_STATUS` arrives later, the agent will try to apply the operation, but this is incorrect since the total resources has already been updated.