ebizboy opened a new issue, #50742:
URL: https://github.com/apache/airflow/issues/50742
### Apache Airflow version
3.0.1
### If "Other Airflow 2 version" selected, which one?
_No response_
### What happened?
The EcsRunTaskOperator fails immediately upon execution after upgrading to
Airflow 3.0.1. The following error log is produced:
```
[2025-05-18, 06:20:39] ERROR - Task failed with exception: source="task"
AttributeError: 'RuntimeTaskInstance' object has no attribute 'key'
File
"/opt/bitnami/airflow/venv/lib/python3.12/site-packages/airflow/sdk/execution_time/task_runner.py",
line 838, in run
File
"/opt/bitnami/airflow/venv/lib/python3.12/site-packages/airflow/sdk/execution_time/task_runner.py",
line 1130, in _execute_task
File
"/opt/bitnami/airflow/venv/lib/python3.12/site-packages/airflow/sdk/bases/operator.py",
line 408, in wrapper
File
"/opt/bitnami/airflow/venv/lib/python3.12/site-packages/airflow/providers/amazon/aws/operators/ecs.py",
line 520, in execute
File
"/opt/bitnami/airflow/venv/lib/python3.12/site-packages/pydantic/main.py", line
989, in __getattr__
```
This operator was working correctly in previous versions (e.g., Airflow
2.10.5 as mentioned in a related discussion). It seems an attribute key is
expected from the RuntimeTaskInstance object but is no longer available or has
been renamed in Airflow 3.0.1.
### What you think should happen instead?
It should execute normally, as it did in versions prior to Airflow 3.0.0.
### How to reproduce
Run a simple DAG that includes an EcsRunTaskOperator
### Operating System
eks amazon linux 2023
### Versions of Apache Airflow Providers
apache-airflow-providers-amazon 9.7.0
### Deployment
Other 3rd-party Helm chart
### Deployment details
bitnami airflow chart 24.0.1
### Anything else?
_No response_
### 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]
