[
https://issues.apache.org/jira/browse/AMBARI-23110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko resolved AMBARI-23110.
-----------------------------------------
Resolution: Fixed
> livy2-client version is not updated as part of Patch Upgrade.
> -------------------------------------------------------------
>
> Key: AMBARI-23110
> URL: https://issues.apache.org/jira/browse/AMBARI-23110
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.6.2
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Priority: Critical
> Labels: pull-request-available
> Fix For: 2.6.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> *STR*
> 1) Deployed cluster with Ambari version: 2.6.1.0-143 and HDP version:
> 2.6.4.0-91
> 2) Upgrade Ambari to Target Version: 2.6.2.0-67
> 3) Patch Express Upgrade Spark2 to HDP-2.6.5.0-120
> Observe the version of livy2-client after PU
> result of hdp-select command
> {code:java}
> [root@ctr-e138-1518143905142-45389-01-000002 ~]# hdp-select | grep
> livy2-client
> livy2-client - 2.6.4.0-91
> [root@ctr-e138-1518143905142-45389-01-000002 ~]#
> {code}
> hdp-select outputs <See the livy2-client versions on all hosts , should have
> been 2.6.4.0-120>
> {code:java}
> ===6===
> livy2-client - 2.6.4.0-91
> livy2-server - 2.6.5.0-120
> ===2===
> livy2-client - 2.6.4.0-91
> livy2-server - 2.6.4.0-91
> ===5===
> livy2-client - 2.6.4.0-91
> livy2-server - 2.6.4.0-91
> ===4===
> livy2-client - 2.6.4.0-91
> livy2-server - 2.6.4.0-91
> {code}
> *Note : The livy2-client version was set correctly during Full stack Express
> Upgrade. The issue is seen only for Patch Upgrade*
> LIVY2_CLIENT isn't actually a component which Ambari manages. That's why it's
> never orchestrated. I suppose that we can fix this by having the
> SPARK2_CLIENT also update the pointers for LIVY2_CLIENT by changing the
> stack_packages.json.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
