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
Describe the bug
I'm using vault with nomad to run influxdb job and provide credentials to various other jobs (telegraf, etc.) through vault influxdb secrets engine. When I stop the nomad job, it revokes the given lease, after which the vault crashes.
I'm not sure if this is vault or nomad bug, but either way, I find my vault instance restarted and sealed because of this. I have started to see this behaviour after updating vault from 1.1.0 to 1.1.2 and nomad from 0.8.7 to 0.9.1.
Vault Logs
It looks like vault revokes the influxdb lease correctly ( database/creds/monitor ), then fails to revoke two postgres leases (one is the role that is no longer existing, another a role that has some table ownerships, so it can't be revoked), after which it crashes. From the stacktrace it seems like it has some issue with influxdb lease, even tough it logged a successful revoke.
Hello - when you mention "When I stop the nomad job, it revokes the given lease, after which the vault crashes.", could you clarify what specifically is revoking the lease? Is the Nomad job doing it at termination?
Describe the bug
I'm using vault with nomad to run influxdb job and provide credentials to various other jobs (telegraf, etc.) through vault influxdb secrets engine. When I stop the nomad job, it revokes the given lease, after which the vault crashes.
I'm not sure if this is vault or nomad bug, but either way, I find my vault instance restarted and sealed because of this. I have started to see this behaviour after updating vault from
1.1.0
to1.1.2
and nomad from0.8.7
to0.9.1
.Vault Logs
It looks like vault revokes the influxdb lease correctly (
database/creds/monitor
), then fails to revoke two postgres leases (one is the role that is no longer existing, another a role that has some table ownerships, so it can't be revoked), after which it crashes. From the stacktrace it seems like it has some issue with influxdb lease, even tough it logged a successful revoke.The text was updated successfully, but these errors were encountered: