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
Almost immediately after the update, nomad services on all workload nodes started to produce the following errors every several minutes. We have not noticed any problems apart from logs contamination for now.
[ERROR] client.vault: error during renewal of lease or token failed due to a non-fatal error; retrying: name=default error=<nil> period="2025-01-24 10:09:41.553771101 +0200 EET m=+65278.177218427"
Nomad version was updated from 1.9.1 to 1.9.5
Vault version was updated from 1.17.2 to 1.18.3
We use workload identities for Nomad+Vault integration, and this is our main suspect.
Expected Result
no errors
Actual Result
errors
Nomad Server logs
nothing unusual
Nomad Client logs
The text was updated successfully, but these errors were encountered:
Nomad version
Operating system and Environment details
Debian GNU/Linux 12 (bookworm)
Issue
Almost immediately after the update, nomad services on all workload nodes started to produce the following errors every several minutes. We have not noticed any problems apart from logs contamination for now.
We use workload identities for Nomad+Vault integration, and this is our main suspect.
Expected Result
no errors
Actual Result
errors
Nomad Server logs
nothing unusual
Nomad Client logs
The text was updated successfully, but these errors were encountered: