csherrell commented on issue #10026: URL: https://github.com/apache/airflow/issues/10026#issuecomment-898972082
I am having the same issue. Airflow(2.1.2) / CeleryWorker / BashOperator / run_as_user, running from an Anaconda Environment. I upgraded from 2.0.1 to 2.1.2. For me, this was not happening in 2.0.1. I know this is related to the run_as_user setting in the DAG. I spent the day converting the DAGs over to run as the airflow user and things are working again. Finally! The run_as_user was nice because all the settings for the user's application were in the account. I would have liked to use the run_as_user argument, but it was more important for me to get the data flowing again. I'm willing to help. It is was a lot of work to merge user setting into the airflow account, but toggling back should not be too bad. I use conda and have a 2.0.1 and 2.1.2 environment. I can roll back the install easy enough, but I did do the **airflow db upgrade**, so I would need guidance on an airflow db downgrade. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
