Skip to content
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

client.vault: error during renewal of lease or token failed due to a non-fatal error; retrying: name=default error=<nil> #24933

Open
Himura2la opened this issue Jan 24, 2025 · 0 comments
Labels

Comments

@Himura2la
Copy link

Himura2la commented Jan 24, 2025

Nomad version

Nomad v1.9.5
BuildDate 2025-01-14T18:35:12Z
Revision 0b7bb8b60758981dae2a78a0946742e09f8316f5+CHANGES

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.

[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

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

1 participant