[AMBARI-21391] Use the Correct Effective Stack ID for Commands During an Express Upgrade

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.5.2
• Fix Version/s: 2.5.2
• Epic Link: Cross Stack Name Upgrades
• Assignee: Jonathan Hurley
• Reporter: Jonathan Hurley
• Created: 02/Jul/17 20:09
• Updated: 11/Jul/17 17:21
• Resolved: 04/Jul/17 13:32

Description

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.

    "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"
    },

Issue Links

• links to: Reviewboard