[
https://issues.apache.org/jira/browse/AIRFLOW-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793168#comment-16793168
]
ASF GitHub Bot commented on AIRFLOW-4087:
-----------------------------------------
feng-tao commented on pull request #4916: [AIRFLOW-4087] Don't use sudo to
remove tmp config when no run_as_user
URL: https://github.com/apache/airflow/pull/4916
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Calling SUDO to remove temp cfg file failed
> -------------------------------------------
>
> Key: AIRFLOW-4087
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4087
> Project: Apache Airflow
> Issue Type: Bug
> Reporter: Junda Yang
> Priority: Major
>
> At Lyft we use a non-root user (named *airflow* in our case) to run airflow
> worker and we keep getting emails saying that the user is not in sudoers so
> the command to remove temp airflow.cfg failed.
> {code:java}
> Mar 13 21:22:33 : airflow : user NOT in sudoers ; TTY=unknown ;
> PWD=/srv/airflowinfra ; USER=root ; COMMAND=/bin/rm /tmp/tmpgzw8eaww
> {code}
> I found that the error was generated due to
> [https://github.com/apache/airflow/blob/5a303ebbc572cee7c9c30be84ebf625357360d4b/airflow/task_runner/base_task_runner.py#L155-#L160]
>
> Not having enough context, is there any reason airflow needs to run sudo to
> remove the file? If not, I think it should be safe to remove the sudo,
> because the temp file is owned by the same user who runs worker command.
> {code:java}
> jundayang@airflowinfraworker-production-iad-0184b3e28b386f0cf:/tmp$ ls -la
> tmpzyfuiw2v
> -rw------- 1 airflow airflow 7139 Mar 13 21:25 tmpzyfuiw2v
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
