[AMBARI-15031] Duplicate key violation syncing groups when performing ldap-sync with --all option

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: 2.2.2
• Component/s: ambari-server
• Assignee: Oliver Szabo
• Reporter: Oliver Szabo
• Created: 12/Feb/16 16:58
• Updated: 13/Feb/16 01:34
• Resolved: 12/Feb/16 22:23

Description

While performing an ldap-sync using the --all option, when groups imported from a previous ldap-sync already exist, a duplicate key violation is encountered on the previously existing groups. The duplicate key violation occurs on the UNQ_groups_0 constraint.

Syncing all...........................................................ERROR: Exiting with exit code 1. 
REASON: Caught exception running LDAP sync. Exception EclipseLink-4002 (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException 
Internal Exception: java.sql.BatchUpdateException: Duplicate entry 'mygroup1' for key 'UNQ_groups_0' 
Error Code: 1062

This does not seem of happen when performing an ldap-sync with the --groups option.

Issue Links

• links to: Review Board