[
https://issues.apache.org/jira/browse/AIRFLOW-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16861301#comment-16861301
]
Ash Berlin-Taylor commented on AIRFLOW-4772:
--------------------------------------------
I think that although it generates a new config file it won't be the one that
is used at runtime for tasks -- if you look at {{ps auxwww | grep airflow}}
when a task is running you should see {{airflow run ... -c /tmp/$RANDOM}}
showing that a different config file is in use.
(We should still fix this so we don't generate the wrong config file, but the
right config should be in use for your tasks)
> airflow run_as_user creates new config file when trying to execute a task
> -------------------------------------------------------------------------
>
> Key: AIRFLOW-4772
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4772
> Project: Apache Airflow
> Issue Type: Bug
> Components: DAG
> Affects Versions: 1.10.3
> Environment: Linux centos-7.2.1511
> Reporter: ROHIT K RAMWAL
> Priority: Major
>
> I am using celery executor to scale airflow with redis as backed. Workers are
> executed with airflow user and have priviliges to sudo to other users in the
> system.
> In my config i have set the default_impersonation = 'svc*123' which is a
> default load id for all my jobs. When ever i trigger a job the airflow
> creates a new folder under 'svc*123' and generates a default config which
> fails to identify the original configuration.
> Tried the same with run_as_user which also creates new config first time. If
> we use multiple users to administrate our system better airflow keeps on
> generating new config and default database everytime.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
