nicolamarangoni opened a new issue, #49966:
URL: https://github.com/apache/airflow/issues/49966

   ### Apache Airflow version
   
   3.0.0
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   I'm testing a fresh 3.0.0 installation and started the worker with the 
command `airflow celery worker`, after the usual logs, I see the wollowing 
lines in the logs of the worker service:
   
   ```
   [tasks]
   . execute_workload
   --- Logging error ---
   Traceback (most recent call last):
   File "/usr/local/lib/python3.12/logging/__init__.py", line 464, in format
   return self._format(record)
   File "/usr/local/lib/python3.12/logging/__init__.py", line 460, in _format
   return self._fmt % values
   KeyError: 'task_name'
   During handling of the above exception, another exception occurred:
   Traceback (most recent call last):
   File "/usr/local/lib/python3.12/logging/__init__.py", line 1160, in emit
   msg = self.format(record)
   ....
   ```
   The service looks healthy however, but the installation has no DAGs at the 
moment therefore I didn't testet some DAG executions yet.
   
   
   ### What you think should happen instead?
   
   The `KeyError: 'task_name'` should not happen.
   
   ### How to reproduce
   
   Install a fresh 3.0.0 from the greenfield and launch the worker with the 
command:
   `airflow celery worker`
   
   ### Operating System
   
   Official docker image,
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Other
   
   ### Deployment details
   
   Official docker image running on AWS ECS.
   
   ### 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]

Reply via email to