[
https://issues.apache.org/jira/browse/AMBARI-12188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604827#comment-14604827
]
Hudson commented on AMBARI-12188:
---------------------------------
FAILURE: Integrated in Ambari-branch-2.1 #138 (See
[https://builds.apache.org/job/Ambari-branch-2.1/138/])
AMBARI-12188. Intra stack-version upgrade sends stale configs in commands to
hosts (srimanth) (sgunturi:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=63d074988c1fe2723c97a2183c4327b1250dbd9d)
*
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderHDP22Test.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java
*
ambari-server/src/main/java/org/apache/ambari/server/agent/ExecutionCommand.java
*
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ExecutionCommandWrapper.java
> 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)
