-
Notifications
You must be signed in to change notification settings - Fork 19
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
SIGSEGV on azure role unassignments #190
Comments
Fixed by #191 |
Closing this as there has been a We haven't tested this patch ourself yet, but I'll close this for good measure :) Thanks for the quick fix @vinay-gopalan and @hsimon-hashicorp |
I'm still seeing this issue with 0.17.1 (built into Vault Enterprise 1.16.2):
We've filed Hashicorp support ticket #149475 to track this too. I believe the cause is that the right side of this if rawResponse != nil && (rawResponse.StatusCode == http.StatusNoContent || rawResponse.StatusCode == http.StatusNotFound) {
continue
} |
This is a continued fix from hashicorp#191 (reported in hashicorp#190 ) The issue with the original fix is that Go will still try to evaluate the right side of the `||` operation and try to dereference `.StatusCode` of a `nil` `rawResponse`. Here is a Go playground PoC whipped up by my colleague: https://go.dev/play/p/tu6hOZgv7ZT
We where in the middle of upgrading our vault cluster from 1.15.6 to 1.16.1 when the servers started failing. It seems like there is an issue when azure roles are being unassigned and it causes the vault service to crash.
I suspect the root of this issue is this change from the REST API to the graph API client and that
rawResponse
is stillnil
when we are peeking at thestatusCode
.Traceback:
The text was updated successfully, but these errors were encountered: