[
https://issues.apache.org/jira/browse/AMBARI-12188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604576#comment-14604576
]
Hadoop QA commented on AMBARI-12188:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12742377/AMBARI-12188.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 test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3300//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3300//console
This message is automatically generated.
> Intra stack-version upgrade sends stale configs in commands to hosts
> --------------------------------------------------------------------
>
> Key: AMBARI-12188
> URL: https://issues.apache.org/jira/browse/AMBARI-12188
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Srimanth Gunturi
> Assignee: Srimanth Gunturi
> Fix For: 2.1.0
>
> Attachments: AMBARI-12188.patch
>
>
> When doing an intra stack-version upgrade/downgrade, ambari-server persists
> config-tags to use at the time of upgrade request. This is problematic when
> the upgrade process then changes configs, as the persisted commands have the
> stale tags.
> This is manifested in the case where Hive service upgrade from HDP-2.3.x
> stack-version to HDP-2.3.y stack-version results in HiveServer component not
> starting as both the old and new components use the same configs and conflict
> on the {{hive.server2.thrift.port}} value. The original port is generally
> 10000 and the new port should be 10010. However due to stale configs, both
> the old and new components conflict over the port and the new component does
> not start.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
