Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7AB0C1877C for ; Sat, 13 Feb 2016 01:27:18 +0000 (UTC) Received: (qmail 17727 invoked by uid 500); 13 Feb 2016 01:27:18 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 17699 invoked by uid 500); 13 Feb 2016 01:27:18 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 17688 invoked by uid 99); 13 Feb 2016 01:27:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Feb 2016 01:27:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 0EAAB2C14F4 for ; Sat, 13 Feb 2016 01:27:18 +0000 (UTC) Date: Sat, 13 Feb 2016 01:27:18 +0000 (UTC) From: "Hudson (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-15031) Duplicate key violation syncing groups when performing ldap-sync with --all option MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-15031?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15= 145676#comment-15145676 ]=20 Hudson commented on AMBARI-15031: --------------------------------- SUCCESS: Integrated in Ambari-branch-2.2 #333 (See [https://builds.apache.o= rg/job/Ambari-branch-2.2/333/]) AMBARI-15031. Duplicate key violation during ldap sync (Oliver Szabo (rlev= as: [http://git-wip-us.apache.org/repos/asf?p=3Dambari.git&a=3Dcommit&h=3D2= 89fc18bf436c8a1396d75ed078259474b02c3cb]) * ambari-server/src/test/java/org/apache/ambari/server/security/ldap/Ambari= LdapDataPopulatorTest.java * ambari-server/src/main/java/org/apache/ambari/server/security/ldap/LdapBa= tchDto.java * ambari-server/src/main/java/org/apache/ambari/server/security/ldap/Ambari= LdapDataPopulator.java > Duplicate key violation syncing groups when performing ldap-sync with --a= ll 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=C3=A9r Szab=C3=B3 > Assignee: Oliv=C3=A9r Szab=C3=B3 > Fix For: 2.2.2 > > Attachments: AMBARI-15031.patch > > > While performing an ldap-sync using the {{--all}} option, when groups imp= orted 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.=20 > {noformat} > Syncing all...........................................................ERR= OR: Exiting with exit code 1.=20 > REASON: Caught exception running LDAP sync. Exception EclipseLink-4002 (E= clipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persist= ence.exceptions.DatabaseException=20 > Internal Exception: java.sql.BatchUpdateException: Duplicate entry 'mygro= up1' for key 'UNQ_groups_0'=20 > Error Code: 1062 > {noformat} > This does not seem of happen when performing an ldap-sync with the {{--gr= oups}} option.=20 -- This message was sent by Atlassian JIRA (v6.3.4#6332)