[AMBARI-22723] Ambari Upgrade failed in case if database have no cluster_version table already. The issue with idempotence

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.6.1
• Fix Version/s: 2.6.2
• Component/s: ambari-server
• Assignee: Dmitry Lysnichenko
• Reporter: Dmitry Lysnichenko
• Created: 04/Jan/18 14:40
• Updated: 26/Apr/18 22:31
• Resolved: 26/Apr/18 22:31

Description

AMBARI-21728 and AMBARI-22469 make the upgrade broken in case of several upgrade tries, failing to follow the Idempotent upgrade paradigm.

Issue is with:

protected void executeDDLUpdates() throws AmbariException, SQLException {
Integer currentVersionID = getCurrentVersionID();    <----------------------
dropBrokenFK();
updateServiceComponentDesiredStateTable(currentVersionID); <----------------------
updateServiceDesiredStateTable(currentVersionID); <----------------------
addSelectedCollumsToClusterconfigTable();
updateHostComponentDesiredStateTable();
updateHostComponentStateTable();
dropStaleTables();  <----------------------
updateUpgradeTable();
createUpgradeHistoryTable();
updateRepositoryVersionTable();
renameServiceDeletedColumn();
addLegacyColumn();
expandUpgradeItemItemTextColumn();
addViewUrlPKConstraint();
removeStaleConstraints();
}

getCurrentVersionID() trying to query non-existing table and failing whole upgrade

Issue Links

• links to: review_request_