You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2017/07/11 17:22:01 UTC
[jira] [Commented] (AMBARI-21391) Use the Correct Effective Stack
ID for Commands During an Express Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-21391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082569#comment-16082569 ]
Hudson commented on AMBARI-21391:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1667 (See [https://builds.apache.org/job/Ambari-branch-2.5/1667/])
AMBARI-21391 - Use the Correct Effective Stack ID for Commands During an (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=00cc41b948dd69f0d7a0431960706a0b1618cbf3])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/UpgradeContext.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/stack/upgrade/HostOrderGrouping.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/UpdateDesiredStackAction.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/state/UpgradeHelperTest.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderTest.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/UpgradeActionTest.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/FinalizeUpgradeAction.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClusterEffectiveVersionTest.java
AMBARI-21402 - Fix Unit Test Failures Caused by AMBARI-21391 (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a5ce6b4271663167eb827e98436748d02bcefc2c])
* (edit) ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/UpgradeActionTest.java
* (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/upgrades/config-upgrade.xml
* (edit) ambari-server/src/test/java/org/apache/ambari/server/actionmanager/TestActionDBAccessorImpl.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderHDP22Test.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/FinalizeUpgradeAction.java
* (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/upgrades/config-upgrade.xml
> Use the Correct Effective Stack ID for Commands During an Express Upgrade
> -------------------------------------------------------------------------
>
> Key: AMBARI-21391
> URL: https://issues.apache.org/jira/browse/AMBARI-21391
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.5.2
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21391.patch
>
>
> During an EU, the effective stack ID needs to be correctly determined based on whether the desired stack has changed.
> STR:
> - Create a stack with BIgInsights 4.2.5
> - Register HDP 2.6
> - Perform an EU
> The "STOP" steps should be sending down host_params/stack_version = 4.2.5.0. All commands after the desired stack ID change should adjust to using the target (HDP 2.6) value.
> {code}
> "configuration_credentials": {},
> "roleCommand": "CUSTOM_COMMAND",
> "credentialStoreEnabled": "false",
> "hostLevelParams": {
> "stack_name": "BigInsights",
> "current_version": "4.2.5.0-0000",
> "custom_command": "RESTART",
> "stack_version": "4.2.5",
> ...
> },
> "commandParams": {
> "upgrade_direction": "upgrade",
> "service_package_folder": "common-services/ZOOKEEPER/3.4.5/package",
> "hooks_folder": "HDP/2.0.6/hooks",
> "clusterName": "c1",
> "script": "scripts/zookeeper_server.py",
> "request_id": "10",
> "version": "2.6.0.0-334",
> "forceRefreshConfigTagsBeforeExecution": "true",
> "upgrade_type": "nonrolling_upgrade",
> "command_timeout": "900",
> "script_type": "PYTHON"
> },
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)