ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-22544) Upgrade from Ambari 2.5.2 to 2.6.0 fails
Date Thu, 30 Nov 2017 21:21:00 GMT

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

Hudson commented on AMBARI-22544:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8474 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8474/])
AMBARI-22544. Upgrade from Ambari 2.5.2 to 2.6.0 fails. (mpapirkovskyy) (mpapyrkovskyy: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=195195fac3fc625c21e5229af8130a854998f99b])
* (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


> Upgrade from Ambari 2.5.2 to 2.6.0 fails
> ----------------------------------------
>
>                 Key: AMBARI-22544
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22544
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.6.1
>            Reporter: Myroslav Papirkovskyi
>            Assignee: Myroslav Papirkovskyi
>            Priority: Blocker
>             Fix For: 2.6.1
>
>
> When upgrading from Ambari 2.5.2 to Ambari 2.6.0, we hit this error preventing from completing
the ambari-server upgrade.
> {noformat}
> 20 Nov 2017 11:39:08,115 ERROR [main] SchemaUpgradeHelper:202 - Upgrade failed.
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Cannot delete
or update a parent row: a foreign key constraint fails (`ambari_01`.`clusters`, CONSTRAINT
`FK_clusters_upgrade_id` FOREIGN KEY (`upgrade_id`) REFERENCES `upgrade` (`upgrade_id`))
> {noformat}
> To get around this, he had to restore the db backup from 2.5.3 and adjust a table in
mysql with ‘update clusters set upgrade_id = null’ so a record in the ‘upgrades’ table
could be removed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message