[ 
https://issues.apache.org/jira/browse/AMBARI-23266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated AMBARI-23266:
------------------------------------
    Labels: pull-request-available  (was: )

> Wrong service_package_folder in serviceLevelParams during Express Upgrade 
> from HDP 2.6 to HDP 3.0
> -------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-23266
>                 URL: https://issues.apache.org/jira/browse/AMBARI-23266
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.7.0
>            Reporter: Myroslav Papirkovskyi
>            Assignee: Myroslav Papirkovskyi
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 2.7.0
>
>
> Upgrade HDP 2.6 to HDP 3.0 in Ambari 2.7; EU is supported only (i.e. no RU).
> At upgrade time, when the services are starting we should use the new stack 
> version's _service_package_folder_ instead of the old one. This was ok, until 
> the change in FileCache.get_service_base_dir to get the base directory from 
> 'serviceLevelParams' instead of 'commandParams'.
> {code:java}
>  ...
>  "serviceLevelParams": {
>  "credentialStoreEnabled": false, 
>  "status_commands_timeout": 300, 
>  "version": "2.7.3", 
>  "service_package_folder": "common-services/YARN/2.1.0.2.0/package"
>  },
>  ...
>  "commandParams": {
>  "service_package_folder": "stacks/HDP/3.0/services/YARN/package", 
>  "hooks_folder": "stack-hooks", 
>  "clusterName": "cluster1", 
>  "custom_command": "RESTART", 
>  "upgrade_direction": "upgrade", 
>  "upgrade_type": "nonrolling_upgrade", 
>  "script": "scripts/historyserver.py", 
>  "version": "3.0.0.2-155", 
>  "forceRefreshConfigTagsBeforeExecution": "true", 
>  "request_id": "17", 
>  "command_timeout": "900", 
>  "script_type": "PYTHON"
>  },
> {code}
> The _service_package_folder_ is different; the one in _commandParams_ is the 
> correct value.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to