Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 20 Jul 2015 23:45:04 +0000 (UTC)
From: "Alejandro Fernandez (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12846044.1437184200000.238721.1437435904742@Atlassian.JIRA>
In-Reply-To: <JIRA.12846044.1437184200000@Atlassian.JIRA>
References: <JIRA.12846044.1437184200000@Atlassian.JIRA>
 <JIRA.12846044.1437184200574@arcas>
Subject: [jira] [Updated] (AMBARI-12455) RU - Magician Script to correct
 data inconsistencies, allow retrying repo installation, force finalize to
 versions, etc
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMBARI-12455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alejandro Fernandez updated AMBARI-12455:
-----------------------------------------
    Attachment: gpl_license_3.0.txt
                ru_magician.py
                lgpl_license.txt

> RU - Magician Script to correct data inconsistencies, allow retrying repo installation, force finalize to versions, etc
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-12455
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12455
>             Project: Ambari
>          Issue Type: Story
>          Components: ambari-agent
>    Affects Versions: 2.0.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>             Fix For: 2.1.2
>
>         Attachments: AMBARI-12455.v2.patch, gpl_license_3.0.txt, lgpl_license.txt, ru_magician.py
>
>
> Support has identified the need to come up with a script to fix any mismatches in the database, or identify problems during Rolling Upgrade.
> This can be a simple Python script that,
> * On a newly installed cluster, ensures that there is at least one cluster version whose state is CURRENT. If not, will advise the user to restart services.
> * If the user has Registered and Installed repos, check that each one has a unique version and display name. Further, if any are stuck in an INSTALLING state, will let the user take three potential actions: leave as is, force to INSTALLED, force to INSTALL_FAILED.
> * If the user has Registered and Installed repos, and one cluster_version is already in an UPGRADING state,  perhaps because hdp-select changed the symlinks and a component was restarted, or the user inadvertently started a manual upgrade, will allow the user to force it back to INSTALLED.
> * If the user in the in the middle of an upgrade, and they want to force one of the versions are CURRENT, it will update all DB records accordingly, and set the previously CURRENT version to INSTALLED.
> For now, this will support Ambari 2.0.0 and higher, and MySQL, and Postgres.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)