[ https://issues.apache.org/jira/browse/AIRFLOW-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bolke de Bruin closed AIRFLOW-2870. ----------------------------------- Resolution: Fixed Fix Version/s: 1.10.0 > Migrations fail when upgrading from below > cc1e65623dc7_add_max_tries_column_to_task_instance > -------------------------------------------------------------------------------------------- > > Key: AIRFLOW-2870 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2870 > Project: Apache Airflow > Issue Type: Bug > Reporter: George Leslie-Waksman > Priority: Blocker > Fix For: 1.10.0 > > > Running migrations from below > cc1e65623dc7_add_max_tries_column_to_task_instance.py fail with: > {noformat} > INFO [alembic.runtime.migration] Context impl PostgresqlImpl. > INFO [alembic.runtime.migration] Will assume transactional DDL. > INFO [alembic.runtime.migration] Running upgrade 127d2bf2dfa7 -> > cc1e65623dc7, add max tries column to task instance > Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/base.py", > line 1182, in _execute_context > context) > File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/default.py", > line 470, in do_execute > cursor.execute(statement, parameters) > psycopg2.ProgrammingError: column task_instance.executor_config does not exist > LINE 1: ...ued_dttm, task_instance.pid AS task_instance_pid, task_insta... > {noformat} > The failure is occurring because > cc1e65623dc7_add_max_tries_column_to_task_instance.py imports TaskInstance > from the current code version, which has changes to the task_instance table > that are not expected by the migration. > Specifically, 27c6a30d7c24_add_executor_config_to_task_instance.py adds an > executor_config column that does not exist as of when > cc1e65623dc7_add_max_tries_column_to_task_instance.py is run. > It is worth noting that this will not be observed for new installs because > the migration branches on table existence/non-existence at a point that will > hide the issue from new installs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)