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

Saw a duplciate issue get created in Jira (race condition?) #18

Closed
eriknelson opened this issue Jun 24, 2022 · 1 comment · Fixed by #20
Closed

Saw a duplciate issue get created in Jira (race condition?) #18

eriknelson opened this issue Jun 24, 2022 · 1 comment · Fixed by #20
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/critical Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@eriknelson
Copy link
Member

While triaging this somehow I saw a race condition occur that I think resulted
in two duplicate tickets getting filed:

migtools/crane#83

https://issues.redhat.com/browse/MTRHO-71
https://issues.redhat.com/browse/MTRHO-70

I think what happened here is that I might have added an assignee that caused
a second action to run at the same time as the first, and the labels hadn't
been added yet. I'm not sure how you lock the operation so that this can be
avoided but we'll have to figure out a way to address actions that run in
parallel.

@eriknelson
Copy link
Member Author

Temp workaround for this might be to just wait until the action has recoonciled the ticket into jira during triage to prevent parallel actions.

@eriknelson eriknelson added kind/bug Categorizes issue or PR as related to a bug. priority/critical Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jun 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/critical Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants