[MESOS-4985] Destroy a container while it's provisioning can lead to leaked provisioned directories.

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.28.0
• Fix Version/s: 0.28.1
• Component/s: containerization
• Labels: mesosphere
• Epic Link: Unified Container
• Sprint: Mesosphere Sprint 31
• Story Points: 3
• Assignee: Gilbert Song
• Reporter: Jie Yu
• Shepherd: Jie Yu
• Created: 18/Mar/16 23:21
• Updated: 10/Oct/19 01:48
• Resolved: 23/Mar/16 22:39

Description

Here is the possible sequence of events:
1) containerizer->launch
2) provisioner->provision is called. it is fetching the image
3) executor registration timed out
4) containerizer->destroy is called
5) container->state is still in PREPARING
6) provisioner->destroy is called

So we can be calling provisioner->destory while provisioner->provision hasn't finished yet. provisioner->destroy might just skip since there's no information about the container yet, and later, provisioner will prepare the root filesystem. This root filesystem will not be destroyed as destroy already finishes.

Issue Links

• is related to: MESOS-9964 Support destroying UCR containers in provisioning state