[
https://issues.apache.org/jira/browse/AMBARI-12455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632243#comment-14632243
]
Hadoop QA commented on AMBARI-12455:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12745924/AMBARI-12455.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3422//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3422//console
This message is automatically generated.
> 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.patch
>
>
> 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)
