matteosdocsity commented on issue #30740:
URL: https://github.com/apache/airflow/issues/30740#issuecomment-1515332244

   @dstandish tested now with provider 8.9.0 with no success. Don't know if the 
problem is related with k8s executor only even if the mentioned stdout could 
be...As reported before I can see both logs (even if when the task is running) 
viewable in the UI and both in Google Stackdriver console are related to be 
only internal, like:
   
   `[2023-04-19, 06:39:04 UTC] {taskinstance.py:1309} INFO - Executing 
<Task(TemplatedPythonOperator): hello-task> on 2023-02-15 00:00:00+00:00 
[2023-04-19, 06:39:04 UTC] {standard_task_runner.py:55} INFO - Started process 
36 to run task [2023-04-19, 06:40:15 UTC] {local_task_job.py:276} WARNING - 
State of this instance has been externally set to success. Terminating 
instance. [2023-04-19, 06:40:15 UTC] {process_utils.py:129} INFO - Sending 
Signals.SIGTERM to group 36. PIDs of all processes in the group: [36] 
[2023-04-19, 06:40:15 UTC] {process_utils.py:84} INFO - Sending the signal 
Signals.SIGTERM to group 36 [2023-04-19, 06:40:16 UTC] {process_utils.py:79} 
INFO - Process psutil.Process(pid=36, status='terminated', exitcode=0, 
started='06:39:04') (36) terminated with exit code 0`
   
   I've tested also on 2.5.3 with **docker-compose** (no helm) with both 
Sequential and Local executors with no success.
   
   Going to test now with k8s with airflow 2.4.3


-- 
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]

Reply via email to