apache / apache/airflow

GKEStartPodOperator does not respect execution_timeout when deferrable=True

Open
#71,514 2 comments 0 reactions 1 assignee Claimed by @AyushkhatiDev View on GitHub
area:providers kind:bug provider:google
Dominant language
Python
Stars
46.9k
Forks
17.8k
Avg merge
2d 9h
Merged PRs (30d)
472

Description

### Under which category would you file this issue?

Providers

### Apache Airflow version

3.3.0

### What happened and how to reproduce it?

```python
GKEStartPodOperator(
image="debian:bullseye",
cmds=["bash"],
arguments=["-c", "sleep 480"],
deferrable=True,
execution_timeout=timedelta(minutes=2),
# ...
)
```
instead of the execution timeout causing the job to fail at the 2 minute marks, it chugs along for all 4 minutes and then succeeds.

### What you think should happen instead?

Deferred pods should respect their execution timeout, similar to what was implemented in the Kubernetes provider here:
https://github.com/apache/airflow/pull/67229

### Operating System

_No response_

### Deployment

_No response_

### Apache Airflow Provider(s)

google

### Versions of Apache Airflow Providers

apache-airflow-providers-cncf-kubernetes==10.20.0
apache-airflow-providers-google==22.2.2

### Official Helm Chart version

1.18.0

### Kubernetes Version

_No response_

### Helm Chart configuration

_No response_

### Docker Image customizations

_No response_

### Anything else?

Every single deferrable pod with an execution timeout set does not respect it.

### 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)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.