aurora-issues mailing list archives

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


Charles Raimbert commented on AURORA-1909:

Some useful logs to understand:

D0323 01:08:15.453372 16] Task started.
E0323 01:08:15.571124 16] Traceback (most recent call last):
  File "apache/aurora/executor/", line 119, in _run
    self._start_status_manager(driver, assigned_task)
  File "apache/aurora/executor/", line 168, in _start_status_manager
    status_checker = status_provider.from_assigned_task(assigned_task, self._sandbox)
  File "apache/aurora/executor/common/", line 370, in from_assigned_task
    health_check_user = (os.getusername() if self._nosetuid_health_checks
AttributeError: 'module' object has no attribute 'getusername'

> Thermos Health Check fails for MesosContainerizer if `--nosetuid-health-checks` is set
> --------------------------------------------------------------------------------------
>                 Key: AURORA-1909
>                 URL:
>             Project: Aurora
>          Issue Type: Bug
>          Components: Executor
>            Reporter: Charles Raimbert
>            Assignee: Charles Raimbert
>              Labels: easyfix
> 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:
> {code}
> 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

View raw message