[MESOS-2586] Mesos 0.22 now respects executable flag (or lack of) on URIs

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 0.22.0
• Component/s: fetcher
• Labels: fetcher mesosphere
• Assignee: Niklas Quarfot Nielsen
• Reporter: Sunil Shah
• Shepherd: Bernd Mathiske
• Created: 01/Apr/15 21:22
• Updated: 26/Nov/18 12:32
• Resolved: 26/Nov/18 12:32

Description

I'm unsure if this problem is because of a bug or because a bug has now been fixed.

A number of our Chronos jobs started failing when we upgraded to Mesos 0.22. These worked prior to the upgrade. They specify a URI to a Python script and execute the Python script within a minimal Docker container.

Note that Chronos does not setExecutable on the URI when building the Mesos task and has never done so on URIs (https://github.com/mesos/chronos/blob/36a294d4714e545de91fcda920429faff15a1746/src/main/scala/org/apache/mesos/chronos/scheduler/mesos/MesosTaskBuilder.scala#L101).

stderr output complains about lacking permission:

/bin/sh: 1: ./integration_test.py: Permission denied

I suspect this is intended behaviour and was just wondering if this was a known bug in the fetcher that was fixed in the 0.22 release of Mesos.

Example job configuration:

{
  "schedule": "R/2015-03-13T00:00:00Z/PT1H",
  "name": "Integration Test",
  "container": {
    "type": "DOCKER",
    "image": "mesosphere/python-monitoring"
  },
  "cpus": "1.0",
  "mem": "512",
  "owner": "[e-mail]",
  "uris": [
    "https://path/to/integration_test.py"
  ],
  "command": "cd $MESOS_SANDBOX && ./integration_test.py"
}