From issues-return-65112-archive-asf-public=cust-asf.ponee.io@ambari.apache.org Fri Jan 5 08:47:06 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id C20B7180647 for ; Fri, 5 Jan 2018 08:47:06 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id B1C9B160C3B; Fri, 5 Jan 2018 07:47:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 04265160C19 for ; Fri, 5 Jan 2018 08:47:05 +0100 (CET) Received: (qmail 10811 invoked by uid 500); 5 Jan 2018 07:47:05 -0000 Mailing-List: contact issues-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 issues@ambari.apache.org Received: (qmail 10802 invoked by uid 99); 5 Jan 2018 07:47:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Jan 2018 07:47:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id A33D318094F for ; Fri, 5 Jan 2018 07:47:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -108.011 X-Spam-Level: X-Spam-Status: No, score=-108.011 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id NIggo1yfHFuq for ; Fri, 5 Jan 2018 07:47:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id ED34C5FB37 for ; Fri, 5 Jan 2018 07:47:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id BDCB9E0F55 for ; Fri, 5 Jan 2018 07:47:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 208F1240F2 for ; Fri, 5 Jan 2018 07:47:00 +0000 (UTC) Date: Fri, 5 Jan 2018 07:47:00 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-22419) Ambari upgrade failed 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-22419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312641#comment-16312641 ] Hadoop QA commented on AMBARI-22419: ------------------------------------ {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12904731/AMBARI-22419.trunk.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 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 core tests{color}. The patch passed unit tests in ambari-server. Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12924//console This message is automatically generated. > Ambari upgrade failed > --------------------- > > Key: AMBARI-22419 > URL: https://issues.apache.org/jira/browse/AMBARI-22419 > Project: Ambari > Issue Type: Bug > Components: ambari-sever > Affects Versions: 2.6.0 > Reporter: amarnath reddy pappu > Assignee: Dmytro Grinenko > Fix For: 2.6.2 > > Attachments: AMBARI-22419.branch-2.6.patch, AMBARI-22419.trunk.patch > > > Ambari upgrade would fail during the DMLStatements execution if there is no service definition in the stacks. > For example: Customer database has entry for GANGLIA in alert_definition table but there is no stack definition - hence its getting failed with below exception. > {noformat} > org.apache.ambari.server.AmbariException: Service not found, clusterName=comcastdrcluster, serviceName=GANGLIA > at org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:234) > at org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424) > Caused by: org.apache.ambari.server.ServiceNotFoundException: Service not found, clusterName=comcastdrcluster, serviceName=GANGLIA > at org.apache.ambari.server.state.cluster.ClusterImpl.getService(ClusterImpl.java:864) > at org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1240) > at org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46) > at org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:938) > at org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:231) > ... 1 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.14#64029)