Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BF15817CED for ; Wed, 20 May 2015 14:57:03 +0000 (UTC) Received: (qmail 2940 invoked by uid 500); 20 May 2015 14:57:03 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 2906 invoked by uid 500); 20 May 2015 14:57:03 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 2893 invoked by uid 99); 20 May 2015 14:57:03 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 May 2015 14:57:03 +0000 Date: Wed, 20 May 2015 14:57:03 +0000 (UTC) From: "Dmitry Lysnichenko (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMBARI-11269) Installing Service After Upgrading Stacks Fails Due To Broken Symlink MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Dmitry Lysnichenko created AMBARI-11269: ------------------------------------------- Summary: 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 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)