-
Notifications
You must be signed in to change notification settings - Fork 194
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
bug: portion of the file is locked #1144
Comments
I have exactly the same problem with kubelogin 1.30.0 and reverting to 1.29.0 is a temporary workaround for me (i.e. 1.29.0 from the releases works) 👍 PS <user>> kubectl get nodes
error: get-token: could not write the token cache: json encode error: write C:\Users\<user>\.kube\cache\oidc-login\02e4d5d5d03a8d8ad9f22f2be05cdbca8ee82bd473efca0fd197580bac823c06: The process cannot access the file because another process has locked a portion of the file.
Error: exit status 1 For what it is worth I am also on Win11. |
kubectl-oidc_login.exe get-token --oidc-issuer-url=https://om.......rl/oidc --oidc-client-id=native --oidc-extra-scope=cluster:silnet -v 99 --token-cache-dir D:\
|
I confirm, kubelogin will fail to write/read the cache with my Windows 11 in current version(1.30). Also fixed with downgrading to 1.29. |
Since 1.30 (#1126), it locks the cache file using https://github.com/gofrs/flock. Not working expectedly on Windows? |
I could reproduce this issue in CI as #1146. I will try to fix it. |
Thank you for bringing up the issue. Could you try the new release? |
I confirmed it fixed the issue on my side |
Big thanks @int128 -> v1.30.1 fixes the issue for me! |
Describe the issue
kubelogin does not seem to work after upgrading to 1.30.0
Deleting the file did not solve this
To reproduce
update to version 1.30.0, try to login
Your environment
The text was updated successfully, but these errors were encountered: