[
https://issues.apache.org/jira/browse/AMBARI-12455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680934#comment-14680934
]
Hudson commented on AMBARI-12455:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #3255 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3255/])
AMBARI-12455. RU - Magician Script to correct data inconsistencies, allow
retrying repo installation, force finalize to versions, etc (alejandro)
(afernandez:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3f4153f207be9915d24017220123006066e2482c)
* contrib/ru_magician/README.md
* contrib/ru_magician/ru_magician.py
* contrib/ru_magician/lgpl_license.txt
* pom.xml
* contrib/ru_magician/mit_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.2.0, 2.1.1
>
> Attachments: AMBARI-12455.patch, 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)
