"airflow celery" CLI not working for Airflow 3.0.*

[XD-DENG]

Apache Airflow version

3.0.2

If "Other Airflow 2 version" selected, which one?

No response

What happened?

I have been testing Airflow 3.0.1 and 3.0.2 with Celery provider.

But after installing Celery provider, and when I run any airflow celery XXX CLI command, it fails with the error below:

airflow command error: argument GROUP_OR_COMMAND: invalid choice: 'celery' (choose from 'api-server', 'assets', 'backfill', 'cheat-sheet', 'config', 'connections', 'dag-processor', 'dags', 'db', 'info', 'jobs', 'kerberos', 'plugins', 'pools', 'providers', 'rotate-fernet-key', 'scheduler', 'standalone', 'tasks', 'triggerer', 'variables', 'version'), see help above.

Did I miss anything? Or it's something missed in Airflow 3?

What you think should happen instead?

No response

How to reproduce

pip install apache-airflow==3.0.2 
pip install apache-airflow-providers-celery
airflow celery worker

Operating System

Linux and MacOS

Versions of Apache Airflow Providers

apache-airflow-providers-celery==3.11.0

Deployment

Other

Deployment details

No response

Anything else?

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[XD-DENG]

Actually the same potential issue also applied to fab provider. After I install fab provider, when I run airflow users, I get the same error:

airflow command error: argument GROUP_OR_COMMAND: invalid choice: 'users' (choose from 'api-server', 'assets', 'backfill', 'cheat-sheet', 'config', 'connections', 'dag-processor', 'dags', 'db', 'info', 'jobs', 'kerberos', 'plugins', 'pools', 'providers', 'rotate-fernet-key', 'scheduler', 'standalone', 'tasks', 'triggerer', 'variables', 'version'), see help above.

[XD-DENG]

Ok, so it appears when I set to use CeleryExecutor. This issue report is invalid

[giant-techie01]

Did you find a fix for this? Currently in the same boat

[potiuk]

Ok, so it appears when I set to use CeleryExecutor. This issue report is invalid

If you are in the same boat @giant-techie01 setting CeleryExecutor should help.

[giant-techie01]

It did, thank you!