Skip to content

Fix edge3 executor startup crash on Airflow < 3.2#62593

Merged
dheerajturaga merged 1 commit intoapache:mainfrom
dheerajturaga:bugfix/edge3-backward-compat
Feb 27, 2026
Merged

Fix edge3 executor startup crash on Airflow < 3.2#62593
dheerajturaga merged 1 commit intoapache:mainfrom
dheerajturaga:bugfix/edge3-backward-compat

Conversation

@dheerajturaga
Copy link
Member

db_managers was introduced in ProvidersManager in Airflow 3.2, so loading the edge executor on older versions raised an AttributeError. Guard the access with hasattr so the executor starts cleanly on all supported versions.

  db_managers was introduced in ProvidersManager in Airflow 3.2, so loading the edge executor on older versions raised an AttributeError. Guard the access with hasattr so the executor starts cleanly on all supported versions.
@dheerajturaga dheerajturaga merged commit a46ab40 into apache:main Feb 27, 2026
161 of 162 checks passed
AkshayArali pushed a commit to AkshayArali/airflow_630 that referenced this pull request Feb 28, 2026
db_managers was introduced in ProvidersManager in Airflow 3.2, so loading the edge executor on older versions raised an AttributeError. Guard the access with hasattr so the executor starts cleanly on all supported versions.
AkshayArali pushed a commit to AkshayArali/airflow_630 that referenced this pull request Feb 28, 2026
db_managers was introduced in ProvidersManager in Airflow 3.2, so loading the edge executor on older versions raised an AttributeError. Guard the access with hasattr so the executor starts cleanly on all supported versions.
Copy link
Contributor

@jscheffl jscheffl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool! Thanks for the fix - had no time testing a clean setup with 3.0 or 3.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:providers provider:edge Edge Executor / Worker (AIP-69) / edge3

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants