[
https://issues.apache.org/jira/browse/AMBARI-11269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14552662#comment-14552662
]
Hadoop QA commented on AMBARI-11269:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12734140/AMBARI-11269.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/2791//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/2791//console
This message is automatically generated.
> 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)
