Project

General

Profile

Actions
Copy link

Defect #579

closed

duplicate id when trying to provision objects

Added by Marcel Poul almost 7 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Vít Švanda
Category:
Account managment
Target version:
Citrine (7.3.0)
Start date:
07/14/2017
Due date:
% Done:

100%

Estimated time:
Affected versions:
Owner:

Description

This behaviour occures "randomly" when we resave obejects that supports provisioning e.b. Identities, Roles, TreeNodes. Some of the entities resaves ends up with with error "Caused by: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "ux_account_uid"
Detail: Key (uid, system_id)=(6214352, \xf5834cb67c564523b9225ed14fbac6a5) already exists."

After some research, we think this is because provisioning that performs the UPDATE operation (so the account is linked with identity/role/treenode) sometimes tries to create new account in idm with the same uid that already exists. This is a problem, since we are not able to fill the managed system with data.

Actions
Copy link
 #1

Updated by Jan Helbich almost 7 years ago

Temporary manual fix:
  • grep account uids from log: ```#> grep -i "Provisioning event start" logs/catalina.out
  • delete duplicate sys system entities from Accounts agenda
Actions
Copy link
 #2

Updated by Marcel Poul almost 7 years ago

uid for synchronization and provisioning are the same for the system (LDAP). It seems to be something wrong about the synchronization and provisioning when they run in some specific order. Or maybe the "link account" operation for "not linked" state has some bug.

Actions
Copy link
 #4

Updated by Vít Švanda almost 7 years ago

Problem may be occours during rename AccAccount.uid (after provisioning). In case when for new uid value already exist some other AccAccount with same uid.

Actions
Copy link
 #5

Updated by Vít Švanda almost 7 years ago

  • Status changed from New to In Progress
  • Assignee changed from Radek Tomiška to Vít Švanda
Actions
Copy link
 #6

Updated by Vít Švanda almost 7 years ago

  • Status changed from In Progress to Needs feedback
  • Assignee changed from Vít Švanda to Ondřej Kopr

The problem was resolved by reconfiguration of the IDM systems.

Actions
Copy link
 #7

Updated by Ondřej Kopr almost 7 years ago

  • Status changed from Needs feedback to Resolved
  • Assignee changed from Ondřej Kopr to Vít Švanda
  • % Done changed from 0 to 100

I created same scenario as on project (sync, provisioning, treeNode, different uid), uid was changed and constraint error with ux_account_uid wasnt throw. Thank you for fixing this bug.

Actions
Copy link
 #8

Updated by Vít Švanda almost 7 years ago

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: Atom PDF