Closed colinglaes closed 3 years ago
Thanks for opening your first issue here! Be sure to follow the issue template!
You probably have Airflow installed in --editable
mode from sources rather than packages.
You should remove the 'apache-airflow-providers*' if you install airflow in --editable mode (Though I would argue this is not the best Idea to run airflow in --editable mode in production. (Though I am kind of surprised how many people do that).
You can achieve that by setting INSTALL_PROVIDERS_FROM_SOURCES
variable to true
This has been already addressed in #13439 in 2.0.1
@colinglaes - was my diagnosis correct? Did you manage to fix the problem?
I am looking at similar problem so I might come back with it
@potiuk Thanks for following up, I didn't use that flag when installing. Let me purge my installation and go through the installation steps again, retain the command and output history from the terminal here to give you better context.
@potiuk I just went through the process again and have successfully got the scheduler and webserver running. I believe that the source of my issue was that i had some apache_airflow_providers_*
installed under /usr/local/lib/python3.6/dist-packages
and others under /home/cglaes/.local/lib/python3.6/site-packages
from earlier botched attempts that i hadn't removed in my last installation attempt.
I did have some thoughts though as to how the documentation / error messages could be improved though
https://airflow.apache.org/docs/apache-airflow/stable/installation.html
pip upgrade --pip==20.2.4
is an invalid commandMessages from airflow upgrade_check
fernet_key = None
instead of saying it "must be explicitly set empty". Not everyone knows what empty means in this case (i could see many people setting it like fernet_key =
)comes up and recommends removing the deprecated keys, additionally it states "Please generate a pod_template_file by running
airflow generate_pod_template`", there isn't an explicit statement that running this command is conditional on having a Kubernetes setup. Maybe these checks could be separated to improve clarity.Let me know if it would be helpful for you guys if i paste the output from my terminal
@potiuk I just went through the process again and have successfully got the scheduler and webserver running. I believe that the source of my issue was that i had some
apache_airflow_providers_*
installed under/usr/local/lib/python3.6/dist-packages
and others under/home/cglaes/.local/lib/python3.6/site-packages
from earlier botched attempts that i hadn't removed in my last installation attempt.
Cool.
I did have some thoughts though as to how the documentation / error messages could be improved though
https://airflow.apache.org/docs/apache-airflow/stable/installation.html
pip upgrade --pip==20.2.4
is an invalid command
Yep. This is already fixed in the upcoming 2.0.1 version: https://github.com/apache/airflow/blob/master/docs/apache-airflow/installation.rst
Messages from
airflow upgrade_check
- "fernet_key in airflow.cfg must be explicitly set empty as fernet mechanism is enabledby default. This means that the apache-airflow[crypto] extra-packages are always installed.However, this requires that your operating system has libffi-dev installed.". I think it might be clearer to explicitly state that the config key should be set as
fernet_key = None
instead of saying it "must be explicitly set empty". Not everyone knows what empty means in this case (i could see many people setting it likefernet_key =
)- "1. The following invalid keys were found in your airflow.cfg
comes up and recommends removing the deprecated keys, additionally it states "Please generate a pod_template_file by running
airflow generate_pod_template`", there isn't an explicit statement that running this command is conditional on having a Kubernetes setup. Maybe these checks could be separated to improve clarity.Let me know if it would be helpful for you guys if i paste the output from my terminal
Would you be so kind to open Pull Request fixing those messages/statements ?
The Upgrade check is here: https://github.com/apache/airflow/tree/v1-10-stable/airflow/upgrade and it would be great if you could make a PR to v1-10-stable branch to fix those.
Apache Airflow version: 2.0.0
Environment:
uname -a
): Linux orion 5.4.0-60-generic #67~18.04.1-Ubuntu SMP Tue Jan 5 22:01:05 UTC 2021 x86_64 x86_64 x86_64 GNU/LinuxWhat happened:
I got to upgrading to airflow 2 but when i received the following error message when running
airflow db upgrade
What you expected to happen:
Successful upgrade with out
How to reproduce it:
Follow tutorial: https://airflow.apache.org/docs/apache-airflow/stable/installation.html & https://airflow.apache.org/docs/apache-airflow/stable/upgrading-to-2.html
Anything else we need to know: