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 AA95B18AC5 for ; Fri, 12 Feb 2016 16:59:18 +0000 (UTC) Received: (qmail 183 invoked by uid 500); 12 Feb 2016 16:59:18 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 120 invoked by uid 500); 12 Feb 2016 16:59: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 99988 invoked by uid 99); 12 Feb 2016 16:59:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Feb 2016 16:59:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 1ED152C0AFA for ; Fri, 12 Feb 2016 16:59:18 +0000 (UTC) Date: Fri, 12 Feb 2016 16:59:18 +0000 (UTC) From: =?utf-8?Q?Oliv=C3=A9r_Szab=C3=B3_=28JIRA=29?= To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (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 Oliv=C3=A9r Szab=C3=B3 created AMBARI-15031: ------------------------------------- Summary: Duplicate key violation syncing groups when performin= g 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=C3=A9r Szab=C3=B3 Assignee: Oliv=C3=A9r Szab=C3=B3 Fix For: 2.2.2 While performing an ldap-sync using the {{--all}} option, when groups impor= ted from a previous ldap-sync already exist, a duplicate key violation is e= ncountered on the previously existing groups. The duplicate key violation o= ccurs on the {{UNQ_groups_0}} constraint.=20 {noformat} Syncing all...........................................................ERROR= : Exiting with exit code 1.=20 REASON: Caught exception running LDAP sync. Exception EclipseLink-4002 (Ecl= ipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persisten= ce.exceptions.DatabaseException=20 Internal Exception: java.sql.BatchUpdateException: Duplicate entry 'mygroup= 1' for key 'UNQ_groups_0'=20 Error Code: 1062 {noformat} This does not seem of happen when performing an ldap-sync with the {{--grou= ps}} option.=20 -- This message was sent by Atlassian JIRA (v6.3.4#6332)