[MESOS-7770] Persistent volume might not be mounted if there is a sandbox volume whose source is the same as the target of the persistent volume.

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.1.2, 1.2.1, 1.3.0
• Fix Version/s: 1.1.3, 1.2.2, 1.3.1, 1.4.0
• Component/s: containerization
• Labels: mesosphere persistent-volumes
• Target Version/s: 1.1.3, 1.2.2, 1.3.1, 1.4.0
• Epic Link: Unified Container
• Sprint: Mesosphere Sprint 59
• Story Points: 3
• Assignee: Gilbert Song
• Reporter: Jie Yu
• Shepherd: Jie Yu
• Created: 07/Jul/17 21:40
• Updated: 11/Jul/17 22:06
• Resolved: 11/Jul/17 22:06

Description

This issue is only for Mesos Containerizer.

If the source of a sandbox volume is a relative path, we'll create the directory in the sandbox in Isolator::prepare method:
https://github.com/apache/mesos/blob/1.3.x/src/slave/containerizer/mesos/isolators/filesystem/linux.cpp#L480-L485

And then, we'll try to mount persistent volumes. However, because of this TODO in the code:
https://github.com/apache/mesos/blob/1.3.x/src/slave/containerizer/mesos/isolators/filesystem/linux.cpp#L726-L739

We'll skip mounting the persistent volume. That will cause a silent failure.

This is important because the workaround we suggest folks to solve MESOS-4016 is to use an additional sandbox volume.

Issue Links

• is related to: MESOS-4016 Agent allows creation of persistent volume with absolute container_path