You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2018/01/04 14:41:00 UTC
[jira] [Created] (AMBARI-22723) Ambari Upgrade failed in case if
database have no cluster_version table already. The issue with idempotence
Dmitry Lysnichenko created AMBARI-22723:
-------------------------------------------
Summary: Ambari Upgrade failed in case if database have no cluster_version table already. The issue with idempotence
Key: AMBARI-22723
URL: https://issues.apache.org/jira/browse/AMBARI-22723
Project: Ambari
Issue Type: Bug
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Priority: Blocker
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:
{code}
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();
}
{code}
{{getCurrentVersionID()}} trying to query non-existing table and failing whole upgrade
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)