Repository navigation
ImportError: cannot import name '_ENABLE_AIP_52' from 'airflow.settings' #31064
Description
Apache Airflow version
2.6.0
What happened
After updating to Airflow 2.6.0, none of the DAGs can be imported anymore.
What you think should happen instead
The DAGs should be imported like in version 2.5.1.
How to reproduce
The airflow webserver needs to be running. Then navigate to the /home and the errors import errors appear at the top.
Operating System
Ubuntu 22.04.1 LTS
Versions of Apache Airflow Providers
apache-airflow-providers-common-sql==1.3.3
apache-airflow-providers-ftp==3.3.0
apache-airflow-providers-http==4.1.1
apache-airflow-providers-imap==3.1.1
apache-airflow-providers-postgres==5.4.0
apache-airflow-providers-sqlite==3.3.1
Deployment
Other
Deployment details
Airflow is installed via pip on the Ubuntu server system. No containers (nor orchestrators) involved.
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
Activity
boring-cyborg commentedon May 4, 2023
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.
eladkal commentedon May 4, 2023
mmm
_ENABLE_AIP_52was added in #30510 which is targeted for 2.7.0#30509 that uses
_ENABLE_AIP_52was cherry picked for 2.6.0cc @ephraimbuddy @potiuk not sure how this happened but I guess we need 2.6.1 rather quickly?
eladkal commentedon May 4, 2023
@dominik-werner-casra did you modify
settings.pyin some way?potiuk commentedon May 4, 2023
I think you have a broken installation. It almost looks like part of airflow files in your installation come from one airflow version and part comes from another. Can you please take a look at the installation process you have and any custom steps you do there, because I think this problem you have might only happen if somewhere in your installation process you manually replace the settings.py file that comes with airlfow with one that is your custom settings.py - which of course you absoluttely should not do. You have
local_setings.pythat you can replace but the "settings.py" that comes from airflow should never be replaced.potiuk commentedon May 4, 2023
Conveting it to a discussion. We both wiht @jedcunningham agree there is no way you get this error unless you do something really bad to airflow during installation. We would love to hear what is what you are doing @dominik-werner-casra