stephenonethree commented on issue #16344: URL: https://github.com/apache/airflow/issues/16344#issuecomment-930346798
Here are some further details, although this might be difficult to track down. I have always had 1 copy of the Airflow database. I had Airflow 1.x in my copy of Python 3.6 in `pyenv` (no `virtualenv`). For Airflow 2.x I decided to create a `virtualenv` in my Airflow folder using Python 3.8. So I did that, and merged my settings into the new airflow.cfg. My upgrade from 1.10.15 to Airflow 2.0.2 went fine. It's only once I upgraded to 2.1.2 that I had problems. I think I was probably running the correct Airflow because the `(airflow)` prefix in my command means I had run `pipenv shell` to enter my 2.1.2 virtualenv (I didn't have a virtualenv for 1.10.15) (`airflow` is the name of the virtualenv, which is used as a shell prefix when you have run pipenv shell). I thought it was strange to see an error message `column variable.description does not exist` because my understanding was that `airflow db upgrade` was going to create that column, which is a new column. So the error message seemed a bit "backwards". Anyway, my own problem is resolved. Unfortunately I guess this might not be enough information to reproduce, since now I am successfully upgraded. I would be happy to send along the logs for `airflow db upgrade` but I'm not sure where they are stored (I looked in `logs` but didn't see anything). If Airflow doesn't currently store logs for that command, it might be good to start, to help with future user upgrade issues. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
