Missing crucial packages in the `slim-3.1.0-python3.13` image

[opeida]

Apache Airflow version

3.1.0

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

No response

What happened?

The database migration job failed during migration from apache/airflow:slim-3.0.6-python3.12 to apache/airflow:slim-3.1.0-python3.13. The logs contained the following error (the full log listing is provided below):
ModuleNotFoundError: No module named 'connexion'

After manual installation, the error pointed to the another package.

What you think should happen instead?

The migration job should be completed successfully.

How to reproduce

Run a metadatabase migration job on slim-3.1.0-python3.13.

Operating System

Debian GNU/Linux 12 (bookworm)

Versions of Apache Airflow Providers

apache-airflow-providers-celery==3.12.3
apache-airflow-providers-common-compat==1.7.4
apache-airflow-providers-common-io==1.6.3
apache-airflow-providers-common-sql==1.28.1
apache-airflow-providers-fab==2.4.3
apache-airflow-providers-google==18.0.0
apache-airflow-providers-http==5.3.4
apache-airflow-providers-postgres==6.3.0
apache-airflow-providers-redis==4.3.1
apache-airflow-providers-smtp==2.2.1
apache-airflow-providers-standard==1.8.0

Deployment

Official Apache Airflow Helm Chart

Deployment details

Deployed on GKE with extended image based on apache/airflow:slim-3.0.6-python3.12 and Helm chart 1.18.0.

Anything else?

Log listing

➜  airflow git:(v3) ✗ kubectl logs airflow-run-airflow-migrations-65fr6

2025-09-25 21:26:34 [info     ] Getting connection using `google.auth.default()` since no explicit credentials are provided.
2025-09-25T21:26:36.144111Z [warning  ] No module named 'connexion'    [airflow.configuration] loc=configuration.py:1266
2025-09-25T21:26:36.144975Z [warning  ] cannot load CLI commands from auth manager: The object could not be loaded. Please check "auth_manager" key in "core" section. Current value: "airflow.providers.fab.auth_manager.fab_auth_manager.FabAuthManager". [airflow.cli.cli_parser] loc=cli_parser.py:81
2025-09-25T21:26:36.145143Z [warning  ] Auth manager is not configured and api-server will not be able to start. [airflow.cli.cli_parser] loc=cli_parser.py:82
DB: postgresql://airflow_user:***@airflow-pgbouncer.airflow.svc.cluster.local:6543/airflow-metadata
Performing upgrade to the metadata database postgresql://airflow_user:***@airflow-pgbouncer.airflow.svc.cluster.local:6543/airflow-metadata
2025-09-25T21:26:36.539213Z [info     ] Context impl PostgresqlImpl.   [alembic.runtime.migration] loc=migration.py:211
2025-09-25T21:26:36.539579Z [info     ] Will assume transactional DDL. [alembic.runtime.migration] loc=migration.py:214
2025-09-25T21:26:36.580865Z [info     ] Migrating the Airflow database [airflow.utils.db] loc=db.py:1129
2025-09-25T21:26:36.621483Z [info     ] Context impl PostgresqlImpl.   [alembic.runtime.migration] loc=migration.py:211
2025-09-25T21:26:36.621766Z [info     ] Will assume transactional DDL. [alembic.runtime.migration] loc=migration.py:214
2025-09-25T21:26:36.788401Z [info     ] Context impl PostgresqlImpl.   [alembic.runtime.migration] loc=migration.py:211
2025-09-25T21:26:36.788724Z [info     ] Will assume transactional DDL. [alembic.runtime.migration] loc=migration.py:214
2025-09-25T21:26:36.847099Z [warning  ] No module named 'connexion'    [airflow.configuration] loc=configuration.py:1266
Traceback (most recent call last):
  File "/home/airflow/.local/lib/python3.13/site-packages/airflow/configuration.py", line 1264, in getimport
    return import_string(full_qualified_path)
  File "/home/airflow/.local/lib/python3.13/site-packages/airflow/utils/module_loading.py", line 41, in import_string
    module = import_module(module_path)
  File "/usr/python/lib/python3.13/importlib/__init__.py", line 88, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 1026, in exec_module
  File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
  File "/home/airflow/.local/lib/python3.13/site-packages/airflow/providers/fab/auth_manager/fab_auth_manager.py", line 27, in <module>
    from connexion import FlaskApi
ModuleNotFoundError: No module named 'connexion'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/airflow/.local/bin/airflow", line 7, in <module>
    sys.exit(main())
             ~~~~^^
  File "/home/airflow/.local/lib/python3.13/site-packages/airflow/__main__.py", line 55, in main
    args.func(args)
    ~~~~~~~~~^^^^^^
  File "/home/airflow/.local/lib/python3.13/site-packages/airflow/cli/cli_config.py", line 49, in command
    return func(*args, **kwargs)
  File "/home/airflow/.local/lib/python3.13/site-packages/airflow/utils/cli.py", line 114, in wrapper
    return f(*args, **kwargs)
  File "/home/airflow/.local/lib/python3.13/site-packages/airflow/utils/providers_configuration_loader.py", line 54, in wrapped_function
    return func(*args, **kwargs)
  File "/home/airflow/.local/lib/python3.13/site-packages/airflow/cli/commands/db_command.py", line 207, in migratedb
    run_db_migrate_command(args, db.upgradedb, _REVISION_HEADS_MAP)
    ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/airflow/.local/lib/python3.13/site-packages/airflow/cli/commands/db_command.py", line 135, in run_db_migrate_command
    command(
    ~~~~~~~^
        to_revision=to_revision,
        ^^^^^^^^^^^^^^^^^^^^^^^^
        from_revision=from_revision,
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        show_sql_only=args.show_sql_only,
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/home/airflow/.local/lib/python3.13/site-packages/airflow/utils/session.py", line 100, in wrapper
    return func(*args, session=session, **kwargs)
  File "/home/airflow/.local/lib/python3.13/site-packages/airflow/utils/db.py", line 1142, in upgradedb
    external_db_manager = RunDBManager()
  File "/home/airflow/.local/lib/python3.13/site-packages/airflow/utils/db_manager.py", line 157, in __init__
    auth_manager_db_manager = create_auth_manager().get_db_manager()
                              ~~~~~~~~~~~~~~~~~~~^^
  File "/home/airflow/.local/lib/python3.13/site-packages/airflow/api_fastapi/app.py", line 141, in create_auth_manager
    auth_manager_cls = get_auth_manager_cls()
  File "/home/airflow/.local/lib/python3.13/site-packages/airflow/api_fastapi/app.py", line 128, in get_auth_manager_cls
    auth_manager_cls = conf.getimport(section="core", key="auth_manager")
  File "/home/airflow/.local/lib/python3.13/site-packages/airflow/configuration.py", line 1267, in getimport
    raise AirflowConfigException(
    ...<2 lines>...
    )
airflow.exceptions.AirflowConfigException: The object could not be loaded. Please check "auth_manager" key in "core" section. Current value: "airflow.providers.fab.auth_manager.fab_auth_manager.FabAuthManager".

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

[dada-engineer]

I have worked myself through it and you need flask-appbuilder after installing connexion as well. Then when finished with all package dependencies it installs SQLAlchemy 2.0.43 and the create_engine() will fail

This has been my test for airflow 3.1.0rc2 at least. I guess this is still the same. stick to 3.12 for now.

[yanshil]

I also notice that [fab] are missing in apache/airflow:3.1.0-python3.13 image.

I have to install fab with

RUN pip install 'apache-airflow-providers-fab'

but NOT (THIS WON'T WORKS)

RUN pip install 'apache-airflow[fab]'

After I installed fab, I also got this connextion missing issue. So I also fallback to 3.1.2

[gopidesupavan]

fab is not supported yet for 3.13

[seanfulton]

What about 3.12?
WARNING: There was an error checking the latest version of pip.
ERROR: Could not find a version that satisfies the requirement apache-airflow-providers-flask-appbuilder (from versions: none)
ERROR: No matching distribution found for apache-airflow-providers-flask-appbuilder

Looking through the constraints files, it looks like 3.9 still has the widest support of modules.
Also in one of your install docs, you write that airflow supports Python 3.10, 3.11 and 3.12. If it still supports 3.9 (which the constraints file seems to indicate), it would be good to know.

[potiuk]

Yes FAB provider does not support 3.13 (yet) - but we just merged #50960 - which enables such support - and hopefully the next release of FAB provider will also support Python 3.13 (there are few deps to sort out - including connexion).

So in 3.13 you cannot use yet FABAuthProvider - but you can use the new - experimental - Keycloak Auth Manager - https://airflow.apache.org/docs/apache-airflow-providers-keycloak/stable/auth-manager/index.html or write your own Auth Manager if you want to use Python 3.13 in production (SimpleAuthManager works in 3.13 but should only be used for development and testing).,

ERROR: Could not find a version that satisfies the requirement apache-airflow-providers-flask-appbuilder (from versions: none)
ERROR: No matching distribution found for apache-airflow-providers-flask-appbuilder

You have wrong name. There is no apache-airflow-providers-flask-appbuilder distribution - there is apache-airflow-providers-fab

airflow supports Python 3.10, 3.11 and 3.12. If it still supports 3.9 (which the constraints file seems to indicate

No. The constraint file is an old one and is accidentally available in 3.1.0 tag (and you are not even supposed to look at the files there - you only should look at what is explicitly stated in throve classifiers in PyPi and in airflow-core package pyproject.toml and Python package metadata which clearly states:

requires-python = ">=3.10,<3.14"

This is the source of truth for supported python version, not a presence of constraint files. It's quite a leap of faith to believe that 3.9 can be supported based on constraint files present, where it's clearly specified in requires-python which is the canonical (and the only valid) way of specifying supported versions.

BTW - that old 3.9 constraints should be removed from 3.1 branch (and 3.1.0 tag). I can do some cleanup and add it to release docs after my vacations - but @kaxil @gopidesupavan @eladkal -> maybe you can do it before :)

[potiuk]

Added #56176 to clarify it in the Dockerfile changelog.