[
https://issues.apache.org/jira/browse/AMBARI-21965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167763#comment-16167763
]
Hadoop QA commented on AMBARI-21965:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12887323/AMBARI-21965.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level [trunk
compilation|https://builds.apache.org/job/Ambari-trunk-test-patch/12235//artifact/patch-work/trunkJavacWarnings.txt]
may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12235//console
This message is automatically generated.
> Tez UI: DAG - All Task Attempts displays no records available
> -------------------------------------------------------------
>
> Key: AMBARI-21965
> URL: https://issues.apache.org/jira/browse/AMBARI-21965
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.5.2
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21965.patch, Screen Shot 2017-08-30 at 3.32.52
> PM.png, Tez_UI.png
>
>
> On IOP->HDP upgraded clusters, "testMainUIAndAttemptUIRunningDAG" fails as
> Task Attempts tab in Tez View displays "no records available".
> In the test, we simply run a Tez example jar - mrrsleep, get the relevant
> AppID and DAG ID and look for various pages of Tez UI to reflect expected
> status.
> While rerunning the test, I noticed that the DAG Id(dag_1503917575003_0012_1)
> transitioned from INITED to RUNNING but showed no progress after and the
> tasks attempts page had no records.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
