[jira] [Commented] (AIRFLOW-7116) Tasks get stuck in the "removed" state

["Kamla (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AIRFLOW-7116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17137894#comment-17137894 ] 

Kamla commented on AIRFLOW-7116:
--------------------------------

+1 on this issue for us. we've run into it on 1.10.10 using kubernetes executor 

for us:
person 1 creates a task
person 1 deploys it to our dev environment
person 2 deploys to our dev environment with a different change that doesn't include that task
if person 1 deploys their version again, the tasks show up as removed

If they clear the tasks, those tasks just go back into a removed state
If they clear the dag, it goes back into a removed state
if they try and set the tasks to failed or success, it goes back into a removed state.
Even setting the state directly in the database causes the task to be reset to a removed state.. How is it even getting that the task was in the removed state if its not in the db? 

> Tasks get stuck in the "removed" state
> --------------------------------------
>
>                 Key: AIRFLOW-7116
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-7116
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: DAG
>    Affects Versions: 1.10.9
>         Environment: Mac OS Catalina
> Airflow 1.10.9
> Airflow running locally using out of box sqlite database
>            Reporter: Chris
>            Priority: Major
>              Labels: DAG, local, sqlite, tasks
>         Attachments: Untitled.png
>
>
> This appears to be a regression of:
>  
> https://issues.apache.org/jira/browse/AIRFLOW-1460
>  
> Repro steps:
>  
>  # Configure Dag to run within context manager via "with" keyword.
>  # Comment out one or more tasks within a Dag.
>  # Refresh Dag.
>  # Trigger Dag.
>  # Notice the tasks are removed from the dag and the dag runs the non-commented task(s) successfully.
>  # Uncomment the tasks that were commented before.
>  # refresh dag.
>  # trigger dag.
>  
> Observed results:
>  * The tree view of the dag does not update, showing the re-added tasks.
>  * After Triggering the Dag, (only the task(s) that was/were tested while the others were commented out appears in the Graph View)
>  * On the graph view, the dag's uncommented tasks only appear after restarting Airflow Server/Scheduler.
>  * Even though the Airflow server was restarted, and although the dag now shows all the tasks in both Tree view and Graph view, the dag, when triggered, only runs the task(s) that were previously not commented. 
>  * Note that the tasks when hovering mouse over them in Graph View, show "State" as "removed".
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)