[
https://issues.apache.org/jira/browse/AMBARI-15031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-15031:
----------------------------------
Attachment: AMBARI-15031.patch
> Duplicate key violation syncing groups when performing ldap-sync with --all
> option
> ----------------------------------------------------------------------------------
>
> Key: AMBARI-15031
> URL: https://issues.apache.org/jira/browse/AMBARI-15031
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.0
> Reporter: Olivér Szabó
> Assignee: Olivér Szabó
> Fix For: 2.2.2
>
> Attachments: AMBARI-15031.patch
>
>
> 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.
> {noformat}
> 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
> {noformat}
> This does not seem of happen when performing an ldap-sync with the
> {{--groups}} option.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
