Return-Path: X-Original-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E1358105C7 for ; Wed, 5 Jun 2013 14:48:26 +0000 (UTC) Received: (qmail 82670 invoked by uid 500); 5 Jun 2013 14:48:25 -0000 Delivered-To: apmail-incubator-ambari-dev-archive@incubator.apache.org Received: (qmail 82579 invoked by uid 500); 5 Jun 2013 14:48:24 -0000 Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ambari-dev@incubator.apache.org Delivered-To: mailing list ambari-dev@incubator.apache.org Received: (qmail 82423 invoked by uid 99); 5 Jun 2013 14:48:24 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Jun 2013 14:48:24 +0000 Date: Wed, 5 Jun 2013 14:48:24 +0000 (UTC) From: "Dmitry Lysnichenko (JIRA)" To: ambari-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-2287) The user can get stuck in installation failure loop 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-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-2287: --------------------------------------- Attachment: (was: AMBARI-2287.patch) > The user can get stuck in installation failure loop > --------------------------------------------------- > > Key: AMBARI-2287 > URL: https://issues.apache.org/jira/browse/AMBARI-2287 > Project: Ambari > Issue Type: Bug > Components: agent > Affects Versions: 1.2.4 > Reporter: Dmitry Lysnichenko > Assignee: Dmitry Lysnichenko > Fix For: 1.2.4 > > Attachments: AMBARI-2287.patch > > > Steps to repro: > 1. Install a cluster with Oozie selected. > 2. Cause a installation failure after Oozie succeeded installation. The user is presented with an option to Retry install. > 3. The user goes back to Customize Services, makes config changes, and retries Deploy. > 4. Oozie will cause an installation failure because the schema already exists. The user is presented with an option to Retry install. > 5. Oozie will cause an installation failure because the schema already exists, the user retries install, ad infinitum. > The only way to get out of this mode is to manually drop all tables for Oozie, or change the database name, etc, to avoid the "schema already exists" error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira