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

exec race #209

Open
kfox1111 opened this issue Nov 8, 2024 · 3 comments · May be fixed by #226
Open

exec race #209

kfox1111 opened this issue Nov 8, 2024 · 3 comments · May be fixed by #226
Labels
Milestone

Comments

@kfox1111
Copy link
Contributor

kfox1111 commented Nov 8, 2024

If you have a second update come in too close to the first exec, you can get two exec's happening at once. seen on v0.8.0.

@faisal-memon
Copy link
Collaborator

@kfox1111
Copy link
Contributor Author

Yeah, pretty sure I saw output of two execs interleaved with each other in the journal. Not sure of any other way to have seen output like that. I was testing some stuff out with the spire-ha-agent, which can sometimes trigger two cert returns in short order (spire itself can do this too, just more rare) at the time.

@faisal-memon faisal-memon added this to the 0.10.0 milestone Nov 21, 2024
@faisal-memon
Copy link
Collaborator

Is go spiffe multi threaded? If so that could cause this problem.

If not I see a small window where something like this may happen. We start a go routine here that sets a boolean indicating exec has been run successfully. Before the go routine starts, the function that started go routine exits and another cert update comes in and gets past the check here.

@faisal-memon faisal-memon linked a pull request Dec 5, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants