[AMBARI-15774] Ambari upgrade fails with MySQL DB and enforce gtid enabled

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: 2.2.2
• Component/s: ambari-server
• Assignee: Siddharth Wagle
• Reporter: Siddharth Wagle
• Created: 07/Apr/16 22:20
• Updated: 12/Apr/16 00:26
• Resolved: 11/Apr/16 19:17

Description

Issue: Ambari upgrade is failing from 2.2.0 to 2.2.1.1 with below error:

mbari-server upgrade 
Using python /usr/bin/python 
Upgrading ambari-server 
Updating properties in ambari.properties ... 
WARNING: Can not find ambari.properties.rpmsave file from previous version, skipping import of settings 
WARNING: Can not find ambari-env.sh.rpmsave file from previous version, skipping restore of environment settings 
Fixing database objects owner 
Ambari Server configured for MySQL. Confirm you have made a backup of the Ambari Server database [y/n] (y)? y 
Upgrading database schema 
Error output from schema upgrade command: 
Exception in thread "main" org.apache.ambari.server.AmbariException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException 
Internal Exception: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'ambari.TL_alert_notice' doesn't exist 
Error Code: 1146

Issue Links

• links to: Review board