[MESOS-7703] Mesos fails to exec a custom executor when no shell is used

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.0, 1.2.1, 1.3.0
• Fix Version/s: 1.1.3, 1.2.2, 1.3.1, 1.4.0
• Component/s: agent, executor
• Assignee: Aaron Wood
• Reporter: Aaron Wood
• Shepherd: Jie Yu
• Created: 21/Jun/17 18:59
• Updated: 07/Jul/17 20:12
• Resolved: 07/Jul/17 19:44

Description

If a framework specifies use of its own executor and sets shell to false the executor is never found.

...
I0620 16:27:55.514834 20273 fetcher.cpp:582] Fetched 'http://10.0.2.2:8081/executor' to '/tmp/slave/slaves/c41232ba-fba1-4d6c-866c-35380d85716f-S0/frameworks/c41232ba-fba1-4d6c-866c-35380d85716f-0000/executors/our_executor/runs/b1d11b00-85bf-428a-a1f0-be8de519294e/executor'
Failed to execute command: No such file or directory

Issue Links

• depends upon: MESOS-7768 Implement permissions handling
• is blocked by: MESOS-7764 Move permissions.hpp under posix