Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 5F79C200D44 for ; Mon, 20 Nov 2017 20:49:06 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 5E162160BF9; Mon, 20 Nov 2017 19:49: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 A21ED160BE1 for ; Mon, 20 Nov 2017 20:49:05 +0100 (CET) Received: (qmail 53055 invoked by uid 500); 20 Nov 2017 19:49:04 -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 53046 invoked by uid 99); 20 Nov 2017 19:49:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Nov 2017 19:49:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id EF3A9C7A01 for ; Mon, 20 Nov 2017 19:49:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.811 X-Spam-Level: X-Spam-Status: No, score=-99.811 tagged_above=-999 required=6.31 tests=[KB_WAM_FROM_NAME_SINGLEWORD=0.2, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id e5hHHH4mV93E for ; Mon, 20 Nov 2017 19:49:03 +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 B825D60D82 for ; Mon, 20 Nov 2017 19:49: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 DCCEDE257B for ; Mon, 20 Nov 2017 19:49: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 41443240E6 for ; Mon, 20 Nov 2017 19:49:00 +0000 (UTC) Date: Mon, 20 Nov 2017 19:49:00 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-22469) Ambari upgrade failed MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 20 Nov 2017 19:49:06 -0000 [ https://issues.apache.org/jira/browse/AMBARI-22469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259744#comment-16259744 ] Hadoop QA commented on AMBARI-22469: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12898511/AMBARI-22469.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/12699//console This message is automatically generated. > Ambari upgrade failed > --------------------- > > Key: AMBARI-22469 > URL: https://issues.apache.org/jira/browse/AMBARI-22469 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.6.0 > Reporter: amarnath reddy pappu > Assignee: Dmitry Lysnichenko > Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22469.patch > > > Ambari upgrade would fail for all Ambari view servers. > Steps to reproduce: > 1. Install Ambari 2.5.2 and setup it as view server. (it you don't set up it up as view server also it fails) > 2. now install 2.6.0 > 3. run ambari-server upgrade > it fails out with below exception. > {noformat} > ERROR: Error executing schema upgrade, please check the server logs. > ERROR: Error output from schema upgrade command: > ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException: Unable to find any CURRENT repositories. > at org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:203) > at org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:418) > Caused by: org.apache.ambari.server.AmbariException: Unable to find any CURRENT repositories. > at org.apache.ambari.server.upgrade.UpgradeCatalog260.getCurrentVersionID(UpgradeCatalog260.java:510) > at org.apache.ambari.server.upgrade.UpgradeCatalog260.executeDDLUpdates(UpgradeCatalog260.java:194) > at org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:923) > at org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:200) > ... 1 more > ERROR: Ambari server upgrade failed. Please look at /var/log/ambari-server/ambari-server.log, for more details. > ERROR: Exiting with exit code 11. > REASON: Schema upgrade failed. > {noformat} > For some reason we are checking cluster_version table entries and throwing up above exception. > {noformat} > In UpgradeCatalog260.java > public int getCurrentVersionID() throws AmbariException, SQLException { > List currentVersionList = dbAccessor.getIntColumnValues(CLUSTER_VERSION_TABLE, REPO_VERSION_ID_COLUMN, > new String[]{STATE_COLUMN}, new String[]{CURRENT}, false); > if (currentVersionList.isEmpty()) { > throw new AmbariException("Unable to find any CURRENT repositories."); > } else if (currentVersionList.size() != 1) { > throw new AmbariException("The following repositories were found to be CURRENT: ".concat(StringUtils.join(currentVersionList, ","))); > } > return currentVersionList.get(0); > } > {noformat} -- This message was sent by Atlassian JIRA (v6.4.14#64029)