You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We are using Windows AD with Bitbucket server and saw a set of errors caused when a new user was added to AD.
Bitbucket is attempting to add the new user to a group (based on the AD group), but for some reason the user already exists in that group but with a different id (primary key). The attempt to insert fails as a result of violating the unique constraints.
Here is the SQL statement that fails (names have been changed):
A record for this user already exists in the table, with the same information, but with a different id (primary key).
The existing record has an id of 1572868, while the record being inserted has an id of 1572876.
I'm not sure where (or how) Bitbucket is determining the id to use for inserting into the table.
Can anyone explain why Bitbucket is trying to add this user to the group TWICE?
Should I update the existing record to match the new id Bitbucket is trying to use?