[
https://issues.apache.org/jira/browse/AMBARI-21361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082562#comment-16082562
]
Hudson commented on AMBARI-21361:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1667 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1667/])
AMBARI-21361 - Finalization Can Fail When Host Versions Changed on Stack
(jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6bab5a53789d0c50cc75b1e1397cabcc0630f385])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ExecutionCommandWrapper.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/events/listeners/upgrade/StackVersionListener.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
> Finalization Can Fail When Host Versions Changed on Stack Distribution
> ----------------------------------------------------------------------
>
> Key: AMBARI-21361
> URL: https://issues.apache.org/jira/browse/AMBARI-21361
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.5.2
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21361.patch
>
>
> When attempting to finalize an upgrade between stack vendors, the
> finalization will fail because the service components are stuck in the
> {{IN_PROGRESS}} upgrade state. The problem seems to step from the
> distribution of the new stack. When the stack is distributed, there's no
> existing stack of that kind on the system, therefore the {{stack-select}}
> program is able to link them. This fools {{stack-select status}} into
> thinking that the component is reporting that version.
> {code}
> ambari=> select stack.stack_name, stack_version, hcs.component_name,
> hcs.version, hcs.upgrade_state FROM stack, hostcomponentstate hcs WHERE
> hcs.current_stack_id = stack.stack_id;
> stack_name | stack_version | component_name | version | upgrade_state
> -------------+---------------+------------------+------------+---------------
> BigInsights | 4.2.5 | ZOOKEEPER_SERVER | 2.6.2.0-45 | IN_PROGRESS
> BigInsights | 4.2.5 | ZOOKEEPER_SERVER | 2.6.2.0-45 | IN_PROGRESS
> BigInsights | 4.2.5 | ZOOKEEPER_SERVER | 2.6.2.0-45 | IN_PROGRESS
> BigInsights | 4.2.5 | ZOOKEEPER_CLIENT | 2.6.2.0-45 | IN_PROGRESS
> BigInsights | 4.2.5 | ZOOKEEPER_CLIENT | 2.6.2.0-45 | IN_PROGRESS
> BigInsights | 4.2.5 | ZOOKEEPER_CLIENT | 2.6.2.0-45 | IN_PROGRESS
> {code}
> Because the version has already changed to {{2.6.2.0-45}}, when components
> are restarted during the upgrade, the {{StackVersionListener}} will never
> change the upgrade state to {{COMPLETE}}.
> STR:
> - Install Ambari 2.4.2 with the BigInsights 4.2.5.0 stack
> - Upgrade to Ambari 2.5.2
> - Register HDP 2.6 - at this point, you'll see the problem
> - Perform and upgrade and try to finalize
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
