You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/06/05 03:54:38 UTC
[jira] [Commented] (AMBARI-11700)
YarnTimelineServerStatePreservingCheck does not run when rolling upgrade a
non-HDP stack
[ https://issues.apache.org/jira/browse/AMBARI-11700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573933#comment-14573933 ]
Hadoop QA commented on AMBARI-11700:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12737669/AMBARI-11700.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.WidgetLayoutResourceProviderTest
Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/3041//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/3041//console
This message is automatically generated.
> YarnTimelineServerStatePreservingCheck does not run when rolling upgrade a non-HDP stack
> ----------------------------------------------------------------------------------------
>
> Key: AMBARI-11700
> URL: https://issues.apache.org/jira/browse/AMBARI-11700
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Di Li
> Assignee: Di Li
> Fix For: 2.1.0
>
> Attachments: AMBARI-11700.patch
>
>
> The YarnTimelineServerStatePreservingCheck class skips running the check when the rolling upgrade is for non-HDP stack, due to the comparison against hardcoded stack name "HDP" and version value "2.2.4.2".
> The check may still need to run against a non-HDP stack. Use this JIRA to make the check runnable based on properties (rollingupgrade.stack, rollingupgrade.version) set in the /etc/ambari-server/conf/ambari.properties. Still default to HDP and 2.2.4.2 if the properties do not exist.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)