-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Leases Force Revoke Prefix errors are not ignored #8853
Comments
Thanks for the report! This might be a bug, but I'll let our frontend team investigate on it and determine if that's the case. |
@calvn on Vault 1.8.1 this is still an issue using Oracle & likely all other SQL DBs too. The UI button of Force Revoke Prefix under Access -> Leases doesn't work nor does it behave the same as API / CLI:
|
cc'ing @hashishaw on this one. |
Describe the bug
When trying to force revoke prefix leases via the WebUI, errors aren't ignored. Tried to revoke database leases which arent existing anymore and getting errors like:
There was an error attempting to revoke the prefix: <path>. failed to revoke "<path>/<leaseID>" (1 / 10): failed to revoke entry: resp: (*logical.Response)(nil) err: pq: role "<roleName>" does not exist.
Force revoke via CLI is working fine though:
To Reproduce
Steps to reproduce the behavior:
If there is a situation like described above, the error will occur and the leases aren't getting revoked.
Expected behavior
All leases are revoked successfully
Environment:
vault status
): 1.4.0vault version
): Vault v1.4.0Vault server configuration file(s):
The text was updated successfully, but these errors were encountered: