[
https://issues.apache.org/jira/browse/AMBARI-11700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14579630#comment-14579630
]
Hudson commented on AMBARI-11700:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #2870 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2870/])
AMBARI-11700. YarnTimelineServerStatePreservingCheck does not run when rolling
upgrade a non-HDP stack (Di Li via alejandro) (afernandez:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=721f8a36b02fa4500ad173cc75887bba8d8e26f3)
*
ambari-server/src/test/java/org/apache/ambari/server/checks/YarnTimelineServerStatePreservingCheckTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
*
ambari-server/src/main/java/org/apache/ambari/server/checks/YarnTimelineServerStatePreservingCheck.java
> 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)