You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Warnings {providers_manager.py:156} WARNING - Exception when importing 'airflow.providers.google.leveldb.hooks.leveldb.LevelDBHook' from 'apache-airflow-providers-google' package: No module named 'plyvel' appear in wait-for-airflow-migrations init containers and during webserver pod start.
What you expected to happen
No such warnings, they were not present in 2.1.3 version.
How to reproduce
Install Airflow using airflow helm chart with 2.2.2 airflow docker image and check wait-for-airflow-migrations init containers logs. Warnings can also be seen in webserver container.
Operating System
Debian “buster”
Versions of Apache Airflow Providers
Providers that come with the official Airflow docker image.
Apache Airflow version
2.2.2 (latest released)
What happened
Warnings
{providers_manager.py:156} WARNING - Exception when importing 'airflow.providers.google.leveldb.hooks.leveldb.LevelDBHook' from 'apache-airflow-providers-google' package: No module named 'plyvel'
appear inwait-for-airflow-migrations
init containers and during webserver pod start.What you expected to happen
No such warnings, they were not present in 2.1.3 version.
How to reproduce
Install Airflow using airflow helm chart with 2.2.2 airflow docker image and check
wait-for-airflow-migrations
init containers logs. Warnings can also be seen in webserver container.Operating System
Debian “buster”
Versions of Apache Airflow Providers
Providers that come with the official Airflow docker image.
Deployment
Official Apache Airflow Helm Chart
Deployment details
No response
Anything else
Looking at commit history, isn't this supposed to be a debug level log as per 2f32df7#diff-c56df299b30e60d690494057a4e8721d36406c0cca266961ff2ae6504993c8cb ?
Seems like this logic was changed in 29aab64#diff-c56df299b30e60d690494057a4e8721d36406c0cca266961ff2ae6504993c8cbL288 since
_sanity_check
doesn't handleImportError
s as debug messages . Should these warnings be ignored for now?Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: