Task Killed because Recorded pid does not match the current pid

[BPhadael]

Apache Airflow version

2.9.0

If "Other Airflow 2 version" selected, which one?

No response

What happened?

I created a dag_executor_user as a primary user to run DAGs, while using the airflow user to run the processes (webserver, scheduler, worker). When the dag executor user is set in default impersonation it cannot run DAGs that use the bash operator (this is expected), but when setting run_as_user = airflow in the DAG, tasks fail with the following errors:

WARNING - Recorded pid 10310 does not match the current pid 10316
Sending the signal 15 to group 10316
ERROR - Received SIGTERM. Terminating subproccess

What you think should happen instead?

Expecting task to run as the airflow user (which had no trouble running tasks before adding the dag executor user with default impersonation)

How to reproduce

1. Create second user without sudo permissions
2. Set second user as default_impersonation value in airflow.cfg
3. In a dag using bash operator, set run_as_user to the value of the user running the airflow processes.

Operating System

Amazon Linux 2

Versions of Apache Airflow Providers

No response

Deployment

Docker-Compose

Deployment details

No response

Anything else?

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.