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 C8B7117769 for ; Sat, 27 Jun 2015 15:43:04 +0000 (UTC) Received: (qmail 54850 invoked by uid 500); 27 Jun 2015 15:43:04 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 54818 invoked by uid 500); 27 Jun 2015 15:43:04 -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 54805 invoked by uid 99); 27 Jun 2015 15:43:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 27 Jun 2015 15:43:04 +0000 Date: Sat, 27 Jun 2015 15:43:04 +0000 (UTC) From: "Hadoop QA (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-12101) Ambari : upgrading from 2.0.0 to 2.0.1 wipes out the added service folder on the stack. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-12101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604207#comment-14604207 ] Hadoop QA commented on AMBARI-12101: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12742327/AMBARI-12101.patch against trunk revision . {color:red}-1 patch{color}. The patch command could not apply the patch. Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/3292//console This message is automatically generated. > Ambari : upgrading from 2.0.0 to 2.0.1 wipes out the added service folder on the stack. > --------------------------------------------------------------------------------------- > > Key: AMBARI-12101 > URL: https://issues.apache.org/jira/browse/AMBARI-12101 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.0.0 > Reporter: Dmytro Sen > Assignee: Dmytro Sen > Priority: Critical > Fix For: 2.1.0 > > Attachments: AMBARI-12101.patch > > > - Install Ambari 2.0 based cluster. > - Add a new service (custom) which is not part of the stack using "Add Service" wizard. This step requires the new custom service package needs to be copied to the /var/lib/ambari-server/resources/stacks/HDP/2.2/services folder. > - Deploy the new service and everything works fine. > - Now upgrade from Ambari 2.0 to Ambari 2.0.1 > Problem: The /var/lib/ambari-server/resources/stacks/HDP/2.2/services/mycustomservice folder got wiped out. Restarting the ambari-server results in the following exception. > {code} > 27 May 2015 10:53:55,441 ERROR [main] AmbariServer:667 - Failed to run the Ambari Server > org.apache.ambari.server.StackAccessException: Stack data, stackName=HDP, stackVersion=2.2, serviceName=HST > at org.apache.ambari.server.api.services.AmbariMetaInfo.getService(AmbariMetaInfo.java:497) > at org.apache.ambari.server.api.services.AmbariMetaInfo.getComponent(AmbariMetaInfo.java:265) > at org.apache.ambari.server.controller.utilities.DatabaseChecker.checkDBConsistency(DatabaseChecker.java:96) > at org.apache.ambari.server.controller.AmbariServer.run(AmbariServer.java:217) > at org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:665) > {code} > Expected: After upgrade the added service should be available and active. The custom service folder should not be wiped out from the stacks folder. -- This message was sent by Atlassian JIRA (v6.3.4#6332)