Skip to content
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

Unnecessary warnings during airflow pods starts #20159

Closed
2 tasks done
Aakcht opened this issue Dec 9, 2021 · 2 comments · Fixed by #20172
Closed
2 tasks done

Unnecessary warnings during airflow pods starts #20159

Aakcht opened this issue Dec 9, 2021 · 2 comments · Fixed by #20172
Assignees
Labels
area:core kind:bug This is a clearly a bug

Comments

@Aakcht
Copy link
Contributor

Aakcht commented Dec 9, 2021

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 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.

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 handle ImportErrors as debug messages . Should these warnings be ignored for now?

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@Aakcht Aakcht added area:core kind:bug This is a clearly a bug labels Dec 9, 2021
@boring-cyborg
Copy link

boring-cyborg bot commented Dec 9, 2021

Thanks for opening your first issue here! Be sure to follow the issue template!

@potiuk
Copy link
Member

potiuk commented Dec 9, 2021

Oh yeah it's been on my list as thing to fix! It's really annoying . Let me assign you @Aakcht

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:core kind:bug This is a clearly a bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants