-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Crash at startup with local mount #14750
Comments
- Reported within issue #14750 as a panic, it was identified that we were using the wrong value for local mounts within the table metrics.
Hi @pbriet! Thanks for the bug report, I agree with your conclusion and have submitted a fix for the table metric which should address the panic. What is unclear to me still though is how within your environment managed to get a nil value for the raw variable. That shouldn't ever happen from my understanding, so additional insight on your setup might be useful. The only way I managed to reproduce the issue was to zero out the |
Hi @stevendpclark . Thanks for the fix. What do Maybe this crash hides another error that will occur once the patch is released, let's see. Which elements could I provide to help you digging?
Thanks, |
Aren't we in this case ? (no write on coreMountConfigPath) |
Hi @pbriet, So the mount points under the raw variable are core to Vault and/or are marked for replication (no matter if you are setup for replication or not). The default is for the paths to be within raw (replicated) and should always contain at least the /sys and /identity mount points. These two are critical to Vault and the only time they shouldn't exist, to my knowledge, is before the rawLocal will contain mount paths that have been enabled/setup with the local argument set when creating the mount path , see https://www.vaultproject.io/docs/commands/secrets/enable#local As an example on an initial setup of Vault post If raw is nil basically that means that something wiped out the data/core/_mounts file with the storage backend you are currently using. That is pretty horrible and I don't believe even with the bugfix that you will recover from it. At this point I can't see what could possibly do that but I'm really not familiar with OpenShift and mounted PVCs. |
Thanks for your feedback. Maybe one operator is messing with the data, or the storage gets corrupted (unlikely, but...) Best regards, |
* Address incorrect table metric value for local mounts - Reported within issue #14750 as a panic, it was identified that we were using the wrong value for local mounts within the table metrics. * Add changelog
Hi @pbriet Thanks again for the bug report. I'll close this issue out for now, the fix should be included within the next minor releases of Vault 1.9 and 1.10. |
Describe the bug
Vault crashes after being unsealed :
To Reproduce
Vault has been installed through the Banzai Cloud operator on Openshift.
It works correctly, but at some point, when restarting the pod, it fails to start. The crash occurs once the unsealing process is finalized.
It is configured with a local storage (non-replicated)
Code Analysis
Something looks odd to me. In
loadMounts
(https://github.com/hashicorp/vault/blob/main/vault/mount.go#L995), it seems thatraw
andrawLocal
can both be nil.In our case,
raw
is probably nil here : https://github.com/hashicorp/vault/blob/main/vault/mount.go#L1038Not sure what this means though
Environment:
vault-config.json
The text was updated successfully, but these errors were encountered: