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

2018-01-04 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/AMBARI-22723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311739#comment-16311739
 ] 

Hadoop QA commented on AMBARI-22723:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12904605/AMBARI-22723.patch
  against trunk revision .

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/12922//console

This message is automatically generated.

> 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
>  Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.6.2
>
> Attachments: AMBARI-22723.patch
>
>
> 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)


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

2018-01-04 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/AMBARI-22723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311724#comment-16311724
 ] 

Hudson commented on AMBARI-22723:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8574 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/8574/])
AMBARI-22723. Ambari Upgrade failed in case if database have no (dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dfb97855196ff3e40ae4b6742eabe31082560fe6])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/DBAccessorImpl.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog260.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog260Test.java


> 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
>  Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.6.2
>
> Attachments: AMBARI-22723.patch
>
>
> 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)


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

2018-01-04 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/AMBARI-22723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311611#comment-16311611
 ] 

Hudson commented on AMBARI-22723:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #563 (See 
[https://builds.apache.org/job/Ambari-branch-2.6/563/])
AMBARI-22723. Ambari Upgrade failed in case if database have no (dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b5da60b5ac51637e0448c3df0662a58f477cefbf])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/DBAccessorImpl.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog260Test.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog260.java


> 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
>  Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.6.2
>
> Attachments: AMBARI-22723.patch
>
>
> 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)


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

2018-01-04 Thread Dmitry Lysnichenko (JIRA)

[ 
https://issues.apache.org/jira/browse/AMBARI-22723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311569#comment-16311569
 ] 

Dmitry Lysnichenko commented on AMBARI-22723:
-

Committed 
To https://git-wip-us.apache.org/repos/asf/ambari.git
   41c362eb97..b5da60b5ac  branch-2.6 -> branch-2.6


> 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
>  Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.6.2
>
> Attachments: AMBARI-22723.patch
>
>
> 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)