Skip to content

connections import are broken in 3.2.1rc2 #65627

@zhaorui2022

Description

@zhaorui2022

Under which category would you file this issue?

Airflow Core

Apache Airflow version

3.2.1rc2

What happened and how to reproduce it?

After upgrading to 3.2.1rc2, our jobs that use airflow connection import starts failing with

2026-04-21 17:54:40.953[SQL: SELECT connection.id AS connection_id, connection.conn_id AS connection_conn_id, connection.conn_type AS connection_conn_type, connection.description AS connection_description, connection.host AS connection_host, connection.`schema` AS connection_schema, connection.login AS connection_login, connection.password AS connection_password, connection.port AS connection_port, connection.is_encrypted AS connection_is_encrypted, connection.is_extra_encrypted AS connection_is_extra_encrypted, connection.team_id AS connection_team_id, connection.extra AS connection_extra 

2026-04-21 17:54:40.953sqlalchemy.exc.OperationalError: (MySQLdb.OperationalError) (1054, "Unknown column 'connection.team_id' in 'field list'")

This was working in 3.1.6. (I don't have info regarding if this was working on 3.2.0 since our jobs deployments happen once a week, and we upgraded from 3.2.0 to 3.2.1rc2 within the same week)

The way we run the connection sync script is that using the official docker image as a base, inside it, we mount a script which generates the connections we need to update/insert inside a tmp file, and then call subprocess to invoke airflow connections import --overwrite to sync the connections.

When checking the table schema, there isn't a column named team_id, and there is only a team_name.

What you think should happen instead?

The command should succeed, referencing team_name, not team_id.

Operating System

No response

Deployment

Other Docker-based deployment

Apache Airflow Provider(s)

No response

Versions of Apache Airflow Providers

No response

Official Helm Chart version

Not Applicable

Kubernetes Version

No response

Helm Chart configuration

No response

Docker Image customizations

Not Applicable

Anything else?

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:corekind:bugThis is a clearly a bugneeds-triagelabel for new issues that we didn't triage yet

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions