[
https://issues.apache.org/jira/browse/AIRFLOW-5796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17001980#comment-17001980
]
ASF GitHub Bot commented on AIRFLOW-5796:
-----------------------------------------
stale[bot] commented on pull request #6451: [AIRFLOW-5796] Fix case when
slot_pool relation is missing
URL: https://github.com/apache/airflow/pull/6451
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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)