[AMBARI-22007] Addition of service component after patching a service still keeps the component at base version

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.6.0
• Fix Version/s: 2.6.0
• Component/s: ambari-server
• Labels: patch-upgrade
• Assignee: Jonathan Hurley
• Reporter: Vivek Sharma
• Created: 20/Sep/17 14:14
• Updated: 04/Oct/19 16:12
• Resolved: 25/Sep/17 12:48

Description

STR

1. Deploy HDP-2.6.0.0 cluster with Ambari-2.6.0.0 (2.6.0.0-102)
2. Register VDF for Storm PU to 2.6.0.3-8
3. Perform a patch RU for Storm
4. Revert the patch
5. Perform a patch EU for Storm
6. Add Supervisor component on one of the hosts
7. 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

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

Issue Links

• links to: ReviewBoard