ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-17317) tez.tez-ui.history-url.base did not get updated after ambari upgrade
Date Tue, 21 Jun 2016 00:27:57 GMT

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

Hadoop QA commented on AMBARI-17317:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12811865/AMBARI-17317.branch-2.4.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/7430//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/7430//console

This message is automatically generated.

> tez.tez-ui.history-url.base did not get updated after ambari upgrade
> --------------------------------------------------------------------
>
>                 Key: AMBARI-17317
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17317
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.0
>            Reporter: DIPAYAN BHOWMICK
>            Assignee: DIPAYAN BHOWMICK
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17317.branch-2.4.patch
>
>
> After upgrading from Ambari 2.2.1.0 to ambari 2.2.2.0 my tez.tez-ui.history-url.base
still pointed to the old version of the tez view URL.
> This caused an issue when user clicked on the AM link for a running tez app and it took
them to the wrong url.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message