Taragolis commented on PR #29447:
URL: https://github.com/apache/airflow/pull/29447#issuecomment-1424981137
Not sure is it changes, breeze itself or something else but I have
interesting behaviour with logs during execution this operator
```console
[2023-02-09, 23:33:53 UTC] {ecs.py:489} INFO - ECS task ID is:
6beb6333b8dc4cf7afbd36b524efd026*** Could not read served logs: Parent instance
<TaskInstance at 0xffff5f2c2590> is not bound to a Session; lazy load operation
of attribute 'trigger' cannot proceed (Background on this error at:
https://sqlalche.me/e/14/bhk3)
*** Found local files:
*** *
/root/airflow/logs/dag_id=test_ecs_operator_reatach/run_id=manual__2023-02-09T23:33:49.777801+00:00/task_id=ecs-task-regular-no-reattach/attempt=1.log
*** Could not read served logs: Parent instance <TaskInstance at
0xffff5f3e0050> is not bound to a Session; lazy load operation of attribute
'trigger' cannot proceed (Background on this error at:
https://sqlalche.me/e/14/bhk3)
*** Found local files:
*** *
/root/airflow/logs/dag_id=test_ecs_operator_reatach/run_id=manual__2023-02-09T23:33:49.777801+00:00/task_id=ecs-task-regular-no-reattach/attempt=1.log
*** Could not read served logs: Parent instance <TaskInstance at
0xffff5f480810> is not bound to a Session; lazy load operation of attribute
'trigger' cannot proceed (Background on this error at:
https://sqlalche.me/e/14/bhk3)
*** Found local files:
*** *
/root/airflow/logs/dag_id=test_ecs_operator_reatach/run_id=manual__2023-02-09T23:33:49.777801+00:00/task_id=ecs-task-regular-no-reattach/attempt=1.log
*** Could not read served logs: Parent instance <TaskInstance at
0xffff5f259310> is not bound to a Session; lazy load operation of attribute
'trigger' cannot proceed (Background on this error at:
https://sqlalche.me/e/14/bhk3)
*** Found local files:
```
--
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]
