ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-11269) Installing Service After Upgrading Stacks Fails Due To Broken Symlink
Date Thu, 21 May 2015 17:36:17 GMT

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

Hudson commented on AMBARI-11269:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #2669 (See [https://builds.apache.org/job/Ambari-trunk-Commit/2669/])
AMBARI-11269. Installing Service After Upgrading Stacks Fails Due To Broken Symlink (dlysnichenko)
(dlysnichenko: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3be87ee559e67dca703e6077f0539f9408de52be)
* ambari-agent/src/test/python/resource_management/TestScript.py
* ambari-common/src/main/python/resource_management/libraries/script/script.py


> Installing Service After Upgrading Stacks Fails Due To Broken Symlink
> ---------------------------------------------------------------------
>
>                 Key: AMBARI-11269
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11269
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11269.patch
>
>
> It's easier to explain this with the steps that reproduced it first:
> # Install some components HDP 2.2 - the RPMs will create {{/usr/hdp/current}} and all
of the symlinks that go along with it, such as {{/usr/hdp/current/hbase-client}} ; However,
do NOT install hbase-client for this example
> # Using Ambari, upgrade your cluster to HDP 2.3 for some core components like HDFS and
YARN. Remember that hbase is not installed.
> # Now that you are on HDP 2.3, you decide you want to add hbase. After executing {{/usr/bin/yum
-d 0 -e 0 -y install 'hbase_2_3_*}}, the {{/usr/hdp/current/hbase-client}} symlink still points
to {{/usr/hdp/2.2.3.0-2611/hbase}}
> This was discovered when upgrading a cluster from HDP 2.2 to 2.3 (which worked successfully)
and then adding in a new service after upgrade. 
> It seems like what we need to do is always invoke hdp-select after installing a new package
since the RPMs won't do that in this scenario since {{/usr/hdp/current}} already exists from
the prior stack install.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message