You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2017/09/20 17:18:00 UTC

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

    [ https://issues.apache.org/jira/browse/AMBARI-22007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16173520#comment-16173520 ] 

Jonathan Hurley commented on AMBARI-22007:
------------------------------------------

This bug will affect adding components to hosts where other versions of the component was already installed. It occurs because Storm was already installed on the machine you added the Supervisor to and the symlinks were already created with the older version. 

Example:
{code:title=After Patch, Before Adding Supervisor}
/usr/hdp/current/storm-client -> /usr/hdp/2.6.0.3-8/storm
/usr/hdp/current/storm-nimbus -> /usr/hdp/2.6.0.3-8/storm
/usr/hdp/current/storm-supervisor -> /usr/hdp/2.6.0.0-102/storm
{code}

The installation of any Storm component causes the symlink for {{storm-supervisor}} to also get created. However, when the upgrade was applied, it didn't upgrade supervisor on this machine since it technically wasn't installed there (at least as far as Ambari is concerned).

Any other test which follows this pattern will fail until I can fix this. However, adding a branch new host should work correctly and install the new version.

> 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
>            Assignee: Jonathan Hurley
>            Priority: Critical
>              Labels: patch-upgrade
>             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)