Alejandro Fernandez created AMBARI-12455:
--------------------------------------------
Summary: RU - 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
Support has identified the need to come up with a script to fix any mismatches
in the database, or identify problems during Rolling Upgrade.
https://docs.google.com/document/d/1MkXNbc9R8Rj11R2WyHsrmDQ2sTGhjYrrOoUPbAdOkEU/edit?disco=AAAAAQ1qHbU
This can be a simple Python/SQL 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)
