[
https://issues.apache.org/jira/browse/AIRFLOW-5796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16960865#comment-16960865
]
Ash Berlin-Taylor commented on AIRFLOW-5796:
--------------------------------------------
This can apply much more generally too - _any_ errors from parsing dag bag
during migration should be captured and not displayed to the user.
> Error in SubdagOperator when resetting DB
> -----------------------------------------
>
> Key: AIRFLOW-5796
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5796
> Project: Apache Airflow
> Issue Type: Improvement
> Components: operators
> Affects Versions: 2.0.0, 1.10.6
> Reporter: Jarek Potiuk
> Priority: Major
>
> There is an error when resetting DB. The migration here:
> *cc1e65623dc7_add_max_tries_column_to_task_instance.py*.
> Which reads DagBag and when reading the DagBag "cannot import
> tests/dags/test_clear_subdag.py" with the root cause:
> *psycopg2.ProgrammingError: relation "slot_pool" does not exist*
> *LINE 2: FROM slot_pool*
> The problem is that SubDagOperator relies on slot_pool relation being present
> but it's not yet ready (because it is added in one of the later migrations).
> It does not cause big problems (the error is caught and ignored and migration
> continue), however it's not really nice to see such error.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
