Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If USAG exists in an org for a user accepting an invite, invite process fails #310

Open
glasschef opened this issue May 28, 2015 · 3 comments
Assignees
Labels
Status: To be prioritized Indicates that product needs to prioritize this issue. Triage: Confirmed Indicates and issue has been confirmed as described. Type: Enhancement Adds new functionality.

Comments

@glasschef
Copy link
Contributor

Sometimes USAGs get created as part of an org association request that fails halfway through, and this hanging USAG conflicts when adding USAGs during invitations.

method=PUT; path=/users/someuser/association_requests/1bda9eda555383fab4f813b3d79491e7; status=500; req_id=8f5763af-03b8-4adc-b004-d0fdc3c3cfd1; org_name=someorg; msg={usag_creation_failed,{conflict,<<"duplicate key value violates unique cons"...>>}}

Can we just ignore duplicate USAGs for this scenario and complete the invite?

@marcparadise
Copy link
Member

I'll need to research it - I think we can at least handle the automatic removal of it, if not actually verify that it's still safe to use the group already present.

@sean-horn
Copy link
Contributor

Another possibly related case would be restoration of a preexisting user in a destination chef server chef/knife-ec-backup#72

@tas50 tas50 added Type: Enhancement Adds new functionality. and removed enhancement labels Jan 4, 2019
@PrajaktaPurohit PrajaktaPurohit added Size: S Status: To be prioritized Indicates that product needs to prioritize this issue. Triage: Confirmed Indicates and issue has been confirmed as described. labels Apr 24, 2020
@PrajaktaPurohit
Copy link
Contributor

User org association is a multi step process, if at any point failure occurs before getting to the end of this process, we should be able to retry and deal with the leftover elements of the failure.

@tas50 tas50 removed the Size: S label May 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: To be prioritized Indicates that product needs to prioritize this issue. Triage: Confirmed Indicates and issue has been confirmed as described. Type: Enhancement Adds new functionality.
Projects
None yet
Development

No branches or pull requests

5 participants