-
Notifications
You must be signed in to change notification settings - Fork 406
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
Race seen in client sync #17
Comments
subscribe |
cc @bobbyrullo |
seen in go 1.5.1 |
@liggitt Thanks for reporting. The race can be fixed by adding a mutex, but I think we need to check the if the provider config is expired before using the key endpoints here https://github.com/coreos/go-oidc/blob/master/oidc/client.go#L181. @bobbyrullo |
Or let the provider syncer hold the lock before syncing. Also let it sync a few second before the the config expires |
cc @ericchiang |
details on k8s failure https://paste.fedoraproject.org/298806/03063144/ go version go1.5.1 linux/amd64 |
Add a RWMutex around a client's provider config to prevent race conditions when updating after syncing. Fixes coreos#17
Add a RWMutex around Client's providerConfig field. Syncing the provider config writes to the field, while numerous other actions read from it. Fixes coreos#17
Update github.com/coreos/go-oidc/... to include coreos/go-oidc#17 which fixes a race condition in the OIDC connector.
Add a RWMutex around Client's providerConfig field. Syncing the provider config writes to the field, while numerous other actions read from it. Fixes coreos#17
reported in openshift/origin#5025 (comment)
The text was updated successfully, but these errors were encountered: