incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Sen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-2287) The user can get stuck in installation failure loop
Date Wed, 05 Jun 2013 15:00:24 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13675993#comment-13675993
] 

Dmitry Sen commented on AMBARI-2287:
------------------------------------

+1
                
> 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

Mime
View raw message