You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
The text was updated successfully, but these errors were encountered: