nicolamarangoni commented on issue #42136: URL: https://github.com/apache/airflow/issues/42136#issuecomment-3144643590
@ralichkov many thanks for the hint! However the token was not the issue. I had indeed a `state mismatch` event, but the table `public.celery_taskmeta` was empty. However I did another research in all logs in AWS CloudWatch and found the root error in the scheduler service. The error was that the IAM policy for the IAM service role didn't allow to use the `default` queue in SQS. The problem is that I wanted Airflow to explicitly use a different queue (as in all our production instances with 2.9.3), but it seems that Airlfow 3.0.x is ignoring the parameter AIRFLOW__OPERATORS__DEFAULT_QUEUE, at least when using SQS. Setting AIRFLOW__OPERATORS__DEFAULT_QUEUE =. default solved the issue but the fact that the scheduler ignores AIRFLOW__OPERATORS__DEFAULT_QUEUE looks a bug to me. Issue https://github.com/apache/airflow/issues/49966 on the other hand persists, so I think it's unrelated. -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
