-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
test: Use NFS by default in test VMs #13983
Conversation
1296bbd
to
c8beae3
Compare
c8beae3
to
5349fe4
Compare
test-runtime |
5349fe4
to
6f07830
Compare
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.
LGTM 🎉 🚀
6f07830
to
b8a22a5
Compare
Note: I've disabled NFS for the Runtime test VM because it leads to permission errors. I will try to debug and re-enable later. |
The new K8sVerifier test compiles some Cilium binaries inside the VM, which can lead to 'interrupted system call' errors. Using NFS should fix it by speeding up the filesystem accesses. This commit switches the test VMs to use NFS by default, thereby enabling NFS in our CI. NFS remains disabled in the CI's Runtime tests because it leads to permission errors [1]. 1 - https://jenkins.cilium.io/job/Cilium-PR-Runtime-4.9/2739/consoleFull Signed-off-by: Paul Chaignon <paul@cilium.io>
b8a22a5
to
afae509
Compare
Backporting this to v1.8 as we will otherwise likely hit interrupted system call errors in the K8sVerifier test (already hitting those when running it locally). |
The new K8sVerifier test compiles some Cilium binaries inside the VM, which can lead to
interrupted system call
errors. Using NFS should fix it by speeding up the filesystem accesses.This pull request switches the test VMs to use NFS by default, thereby enabling NFS in our CI.