mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil Shah (JIRA)" <j...@apache.org>
Subject [jira] [Created] (MESOS-2586) Mesos 0.22 now respects executable flag (or lack of) on URIs
Date Wed, 01 Apr 2015 21:22:53 GMT
Sunil Shah created MESOS-2586:
---------------------------------

             Summary: Mesos 0.22 now respects executable flag (or lack of) on URIs
                 Key: MESOS-2586
                 URL: https://issues.apache.org/jira/browse/MESOS-2586
             Project: Mesos
          Issue Type: Bug
          Components: fetcher
    Affects Versions: 0.22.0
            Reporter: Sunil Shah
            Priority: Minor


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:
{code}
/bin/sh: 1: ./integration_test.py: Permission denied
{code}

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:
{code}
{
  "schedule": "R/2015-03-13T00:00:00Z/PT1H",
  "name": "Integration Test",
  "container": {
    "type": "DOCKER",
    "image": "mesosphere/python-monitoring"
  },
  "cpus": "1.0",
  "mem": "512",
  "owner": "sunil@mesosphere.io",
  "uris": [
    "https://path/to/integration_test.py"
  ],
  "command": "cd $MESOS_SANDBOX && ./integration_test.py"
}
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message