Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 26 May 2016 21:25:12 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12965644.1462553146000.308830.1464297912849@Atlassian.JIRA>
In-Reply-To: <JIRA.12965644.1462553146000@Atlassian.JIRA>
References: <JIRA.12965644.1462553146000@Atlassian.JIRA> <JIRA.12965644.1462553146246@arcas>
Subject: [jira] [Commented] (AMBARI-16289) Upgrade existing capacity
 scheduler view instance after the Remote Ambari Cluster changes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 26 May 2016 21:25:14 -0000


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

Hadoop QA commented on AMBARI-16289:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12805861/AMBARI-16289_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:red}-1 core tests{color}.  The patch failed these unit tests in ambari-server:

                  org.apache.ambari.server.controller.internal.HostResourceProviderTest

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

This message is automatically generated.

> Upgrade existing capacity scheduler view instance after the Remote Ambari Cluster changes
> -----------------------------------------------------------------------------------------
>
>                 Key: AMBARI-16289
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16289
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-views
>            Reporter: Gaurav Nagar
>            Assignee: Gaurav Nagar
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-16289_branch-2.4.patch
>
>
> With https://issues.apache.org/jira/browse/AMBARI-16274 . Capacity scheduler instances which is configured as Custom won't work.
> We need to provide proper upgrade for those instances, so instances will work without any extra configuration after upgrade


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