You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Bjorn Olsen (Jira)" <ji...@apache.org> on 2019/12/08 18:02:00 UTC
[jira] [Commented] (AIRFLOW-6195) queued_dttm is "None" on UI, and
not updated when tasks requeued
[ https://issues.apache.org/jira/browse/AIRFLOW-6195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16990952#comment-16990952 ]
Bjorn Olsen commented on AIRFLOW-6195:
--------------------------------------
Turns out this actually affects several fields, due to them being missing from refresh_from_db() in the TaskInstance model file. Fix incoming
> queued_dttm is "None" on UI, and not updated when tasks requeued
> ----------------------------------------------------------------
>
> Key: AIRFLOW-6195
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6195
> Project: Apache Airflow
> Issue Type: Bug
> Components: ui
> Affects Versions: 1.10.6
> Reporter: Bjorn Olsen
> Assignee: Bjorn Olsen
> Priority: Minor
> Attachments: image-2019-12-08-14-44-56-762.png, image-2019-12-08-14-45-34-266.png, image-2019-12-08-14-46-09-051.png
>
>
> When inspecting a task instance on the UI, the value for queued_dttm displays as 'None' despite having a value in the DB. Also, the value for queued_dttm is from when the task was first queued and not updated if it is requeued - it is not clear if this is intentional behaviour or not.
> On UI:
> !image-2019-12-08-14-44-56-762.png!
> In DB:
> !image-2019-12-08-14-45-34-266.png!
> In reality, task was queued on 8 December and run shortly after.
> queued_dttm in the DB is from the very first attempt, and is not updated from recent attempts.
> !image-2019-12-08-14-46-09-051.png!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)