-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
v1.8 backport: ci: Disable NFS locking #16970
Conversation
[ upstream commit 1dd477d ] This is an attempt to fix the recent issues with NFS locking in CI, e.g. issue cilium#16551 From the nfs(5) manpage: > When using the nolock option, applications can lock files, but such > locks provide exclusion only against other applications running on > the same client. Remote applications are not affected by these locks. Since in CI, we do not have any remote applications accessing the shared folder, only using local locks should be safe and more robust than using distributed locking. Signed-off-by: Sebastian Wicki <sebastian@isovalent.com> Signed-off-by: Kornilios Kourtis <kornilios@isovalent.com>
test-backport-1.8 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Thanks for doing this!
The motivation here is that it is not clear whether #16554 actually causes issues with VM provisioning. If there are no such issues in this PR, then it might be unrelated. Otherwise, we can investigate further. |
I'll try one more time. |
test-upstream-k8s |
test-upstream-k8s |
Magical, it just passes. I don't know why I had such trouble with that PR on my prior backporting attempts. |
The last 1.8 backporting round (#16912), skipped #16554 due to CI failures in the test-upstream-k8s pipeline.
This PR is a backport of just #16554.
Once this PR is merged, you can update the PR labels via: