mesaverde0207 opened a new issue, #29459: URL: https://github.com/apache/airflow/issues/29459
### Apache Airflow version 2.5.1 ### What happened When I ran the Cloud Run jobs execute command in BashOperator: ```Shell gcloud beta run jobs execute extract-dev-****** --project "products-*****" --region "us-east1" --wait ``` And the task failed, and I got an error whose message said that the task process group received SIGTERM: - [bashop_cloud_run_jobs_error.log](https://github.com/apache/airflow/files/10705132/error.log) But It went green when I dropped the "wait" option. ### What you think should happen instead The error message says, "WARNING - Recorded pid 6032 does not match the current pid 6033" and so Airflow sent Signals.SIGTERM to group 6033, whose PIDs of all processes in the group: [6036, 6033]. I think this SIGTERM signal makes the BashOperator crash. ### How to reproduce _No response_ ### Operating System Ubuntu 22.04.1 LTS ### Versions of Apache Airflow Providers apache-airflow-providers-common-sql==1.3.3 apache-airflow-providers-ftp==3.3.0 apache-airflow-providers-google==8.8.0 apache-airflow-providers-http==4.1.1 apache-airflow-providers-imap==3.1.1 apache-airflow-providers-postgres==5.4.0 apache-airflow-providers-sqlite==3.3.1 ### Deployment Virtualenv installation ### Deployment details _No response_ ### Anything else There are some issues similar to this problem: - https://github.com/apache/airflow/issues/17507 - https://github.com/apache/airflow/issues/20992 ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
