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?
Happy Monday community! This week Monday coffee with Jexo welcomed a special guest - @Jari Worsley from Adaptavist to present you the latest news from the Atlassian ecosystem. Thank you fo...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events