abdalhalimalzohbi opened a new issue, #43203: URL: https://github.com/apache/airflow/issues/43203
### Apache Airflow Provider(s) redis ### Versions of Apache Airflow Providers airflow-provider-rabbitmq 0.6.1 ### Apache Airflow version 2.10.2 ### Operating System airflow bitnami image ### Deployment Official Apache Airflow Helm Chart ### Deployment details _No response_ ### What happened When using CeleryExecutor as the core executor for Airflow and utilizing the RabbitMQOperator task from rabbitmq_provider.operators.rabbitmq, the task remains stuck in the queued state and is not recognized by Celery workers. The issue arises when attempting to use RabbitMQOperator to publish messages to an external RabbitMQ queue, which is not related to the Airflow instance. The root cause of the conflict is that the RabbitMQOperator takes a queue field as a parameter, and this value is mistakenly treated as the name of the queue that the Celery workers will use to execute the task. This creates confusion, as the queue parameter is intended to represent the destination queue for message publishing, not the execution queue for Celery tasks. ### What you think should happen instead _No response_ ### How to reproduce NA ### 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]
