ci: Disable NFS locking

[gandro]

This is an attempt to fix the recent issues with NFS locking in CI, e.g.
issue #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.

[gandro]

test-me-please

[gandro]

test-1.20-4.19

Hit a unknown (?) but likely unrelated failure:

/home/jenkins/workspace/Cilium-PR-K8s-1.20-kernel-4.19/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:518
Cannot flush conntrack table
Expected
    <bool>: false
to be true
/home/jenkins/workspace/Cilium-PR-K8s-1.20-kernel-4.19/src/github.com/cilium/cilium/test/k8sT/DatapathConfiguration.go:859

https://jenkins.cilium.io/job/Cilium-PR-K8s-1.20-kernel-4.19/722/testReport/junit/Suite-k8s-1/20/K8sDatapathConfig_Iptables_Skip_conntrack_for_pod_traffic/

[gandro]

test-only --focus="K8sVerifier.Runs the kernel verifier against Cilium." --k8s_version=1.21 --kernel_version=4.9

Edit: As all other CI seems green, I will be running the above test a few times, as it is the one that was known to flake before.

Edit: Focus test passed https://jenkins.cilium.io/job/Cilium-PR-Tests-Kernel-Focus/237/testReport/Suite-k8s-1/21/K8sVerifier_Runs_the_kernel_verifier_against_Cilium_s_BPF_datapath/ ✔️

[gandro]

test-only --focus="K8sVerifier.Runs the kernel verifier against Cilium." --k8s_version=1.19 --kernel_version=5.4

Edit: Passed https://jenkins.cilium.io/job/Cilium-PR-Tests-Kernel-Focus/239/testReport/Suite-k8s-1/19/K8sVerifier_Runs_the_kernel_verifier_against_Cilium_s_BPF_datapath/ ✔️

[gandro]

test-only --focus="K8sVerifier.Runs the kernel verifier against Cilium." --k8s_version=1.21 --kernel_version=4.9

Edit: https://jenkins.cilium.io/job/Cilium-PR-Tests-Kernel-Focus/240/testReport/Suite-k8s-1/21/K8sVerifier_Runs_the_kernel_verifier_against_Cilium_s_BPF_datapath/ Passed ✔️

[gandro]

The k8s-1.16-kernel-netnext failure in looks ephemeral: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-net-next/813/

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal/InRelease  Could not connect to archive.ubuntu.com:80 (2001:67c:1360:8001::23). - connect (113: No route to host) Could not connect to archive.ubuntu.com:80 (2001:67c:1360:8001::24). - connect (113: No route to host) Could not connect to archive.ubuntu.com:80 (91.189.88.152), connection timed out Could not connect to archive.ubuntu.com:80 (91.189.88.142), connection timed out [IP: 91.189.88.142 80]
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal-updates/InRelease  Unable to connect to archive.ubuntu.com:http: [IP: 91.189.88.142 80]
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal-backports/InRelease  Unable to connect to archive.ubuntu.com:http: [IP: 91.189.88.142 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.

[gandro]

test-only --focus="K8sVerifier.Runs the kernel verifier against Cilium." --k8s_version=1.19 --kernel_version=5.4

Edit: https://jenkins.cilium.io/job/Cilium-PR-Tests-Kernel-Focus/241/testReport/Suite-k8s-1/19/K8sVerifier_Runs_the_kernel_verifier_against_Cilium_s_BPF_datapath/ passed ✔️

[gandro]

If this passes reviews, I think this can be merged. It looks like it might fix the locking issue (it passed the flaky test 5 times so far).

[gandro]

test-only --focus="K8sVerifier.Runs the kernel verifier against Cilium." --k8s_version=1.21 --kernel_version=4.9

[gandro]

test-1.20-4.19

Edit: Meant to start test-1.16-netnext

[gandro]

test-1.16-netnext