-
Notifications
You must be signed in to change notification settings - Fork 14.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No module named 'airflow.providers.google.common.hooks.leveldb' #15451
Comments
This I think can be ignored -- it is the webserver trying to load all the providers and it's failing on one, but this is not fatal and shouldn't stop the Webserver working. Did 2.0.1 (or 2.0.0) have this same behaviour? |
Airflow 2.0.1 and 2.0.0 did not have this behaviour. I've been actively checking logs recently with the upgrade to Airflow 2, so I can say that this warning was not there. |
Thanks @ClassyLion. It's a bug (harmless) in definition of the google provider 2.2.0 in fact: In
should be:
|
I'm not sure if it related with mentioned error. But now I'm trying to login to freshly installed airflow 2.0.2 with LDAP integration and I can't login with my credentials. Log of web pod full of mentioned error/warning:
Everything works fine for me with 2.0.0 and 2.0.1 with my credentials from AD. My Airflow running on AKS if it matters. Here is my webserver_config.py (maybe it also will be useful):
|
@KIRY4 - can you see if you have error in your logs similar to:
We think we know what the issue could be (related to Flask Application Builder dpgaspar/Flask-AppBuilder#1581 and we might have a quick fix for that soon. Can you also let us know how you installed Airflow ? Was this the airflow image ? Or another way ? |
I'm building bit customized image using Breeze:
Later deploying it using following Helm chart: https://github.com/airflow-helm/charts/tree/main/charts/airflow on AKS 1.18.14. And yes, I'm getting following in logs from web pod: |
For the future reference @KIRY4 - this is the root cause (added in FAB 3.2.0). For now i fixed constraints viaa #15470 but in a few days when FAB 3.2.3 gets released we will be able to us this: dpgaspar/Flask-AppBuilder#1602 (comment) |
You can rebuild your image with |
BTW. I recommend to use corresponding See the latest documentation for this with nice examples: https://airflow.apache.org/docs/docker-stack/build.html#customizing-the-image It's much simpler now to build the images and when you use docker build commands by default the released packages are used from PYPI to build the image rather than local source code. Unless you want to use latest master, version of Airflow/providers - this is the recommended way now. |
@KIRY4 -> would it be possible that you check if upgrading FAB to 3.2.3 ( released yesterday) fixes the problem? |
@potiuk fixed! now everything works perfect! thank you! I mean that I successfully login but warning still exist in logs: WARNING - Exception when importing 'airflow.providers.google.common.hooks.leveldb.LevelDBHook' from 'apache-airflow-providers-google' package: No module named 'airflow.providers.google.common.hooks.leveldb' |
Yep. This will fixed when we release next Google Provider and you update either the provider or, Airlfow (we plan to release 2.0.3 very soon addressing a small subset of changes + PIP 21 installability). PR here: #15576 |
This is not solved. I am getting the same error. Just tried to create a docker to install the module separately and this is the error I am getting
What I suggest is to install complete package |
It is solved in the most recent version of the google provider (3.0.0). Currently when you install 2.0.2 you get the previous version of provider installed, but you can manually upgrade it - by extending the image and adding
It will be solved by out-of-the-box installation when we release |
Using --upgrade, solved the error. I haven't get it anymore. Thanks for your help. |
I have the same problem during completing command: |
Upgrading dependencies in docker-compose requires you to update the image, not upgrade dependencie manually. You should read more how docker-compose works - see the note in https://airflow.apache.org/docs/apache-airflow/stable/start/docker.html
If you are not ready to manage and build your images, don't use docker compose other than just for quick start. Use local quick start instead: https://airflow.apache.org/docs/apache-airflow/stable/start/local.html |
Apache Airflow version:
2.0.2
Kubernetes version (if you are using kubernetes) (use
kubectl version
):v1.18.18
Environment:
Cloud provider or hardware configuration: AWS
What happened:
Updated to Airflow 2.0.2 and a new warning appeared in webserver logs:
What you expected to happen:
No warning.
How to reproduce it:
Don't know the specific details. Have tried adding
pip install --upgrade apache-airflow-providers-google
but the error was still there.Anything else we need to know:
I am not using LevelDB for anything in my code, as a result I don't understand from where this error is coming.
The text was updated successfully, but these errors were encountered: