aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Charles Raimbert (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AURORA-1909) Thermos Health Check fails for MesosContainerizer if `--nosetuid-health-checks` is set
Date Thu, 23 Mar 2017 00:55:42 GMT
Charles Raimbert created AURORA-1909:
----------------------------------------

             Summary: Thermos Health Check fails for MesosContainerizer if `--nosetuid-health-checks`
is set
                 Key: AURORA-1909
                 URL: https://issues.apache.org/jira/browse/AURORA-1909
             Project: Aurora
          Issue Type: Bug
          Components: Executor
            Reporter: Charles Raimbert


With MesosContainerizer, the sandbox is of type FileSystemImageSandbox and the health check
is performed using a "mesos-containerizer launch" process, but there is actually a code bug
in the way of getting the user under which to run the health check process:

https://github.com/apache/aurora/blob/master/src/main/python/apache/aurora/executor/common/health_checker.py#L370

{code:python}
health_check_user = (os.getusername() if self._nosetuid_health_checks
            else assigned_task.task.job.role)
{code}

If the Aurora scheduler is configured with `--nosetuid-health-checks` then "os.getusername()"
is executed, but the python "os" module does not present a "getusername()" function.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message