Vivek Sharma created AMBARI-22007:
-------------------------------------
Summary: Addition of service component after patching a service
still keeps the component at base version
Key: AMBARI-22007
URL: https://issues.apache.org/jira/browse/AMBARI-22007
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.6.0
Reporter: Vivek Sharma
Priority: Critical
Fix For: 2.6.0
*STR*
# Deploy HDP-2.6.0.0 cluster with Ambari-2.6.0.0 (2.6.0.0-102)
# Register VDF for Storm PU to 2.6.0.3-8
# Perform a patch RU for Storm
# Revert the patch
# Perform a patch EU for Storm
# Add Supervisor component on one of the hosts
# Observe the version of Supervisor on newly added host
*Result:*
Supervisor still shows its version as the base version
Looks like the issue is because while installing packages for Supervisor,
hdp-select sets it at base-version
{code}
2017-09-19 11:20:33,011 - Execute[('ambari-python-wrap', '/usr/bin/hdp-select',
'set', 'storm-supervisor', '2.6.0.0-598')] {'sudo': True}
2017-09-19 11:20:33,061 - After ('ambari-python-wrap', '/usr/bin/hdp-select',
'set', 'storm-supervisor', '2.6.0.0-598'), reloaded module params
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
