Previously it was leaving NodeName unset in many cases. Give all of
the endpoints an explicit NodeName, making them explicitly local in
all the test cases that don't care either way, and explicitly
non-local in those test cases that did care but were previously just
relying on the fact that a nil NodeName would be treated as remote.
Two test contexts were failing because their AfterEach blocks run even
when BeforeEach skips the test (standard Ginkgo behavior). This caused
resetCRIProxyInjector to fail with "CRI Proxy is undefined".
Switched to using DeferCleanup inside BeforeEach instead, which only
runs if BeforeEach succeeds. This is the same pattern the other test
contexts in this file already use.
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
ImagePullTest was using wait.PollUntilContextCancel which has no
timeout, causing tests to hang for hours when the expected container
state is never reached (e.g., ErrImageNeverPull).
Changed to wait.PollUntilContextTimeout with ContainerStatusRetryTimeout
(5 minutes), matching the pattern used by other tests in the same file.
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
The volume/nfs:1.5 image was updated from CentOS 8 to CentOS Stream 9
in commit 9b47a096f4, but this broke NFS server startup because
NFSv2 is no longer supported in RHEL 9 / CentOS Stream 9.
The `-N 2` flag (disable NFSv2) passed to rpc.mountd and rpc.nfsd
causes them to fail with "2: Unsupported version" since there's no
NFSv2 to disable. This prevented rpc.nfsd from starting, causing
NFS mount timeouts in e2e tests.
Fix by removing the `-N 2` flags. NFSv2 is already unavailable in
CentOS Stream 9, so explicitly disabling it is unnecessary.
Red Hat documentation states: "NFS version 2 (NFSv2) is no longer
supported by Red Hat."
Reference: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/managing_file_systems/mounting-nfs-shares_managing-file-systems
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
Replace the TensorFlow-based wide-deep workload with the PyTorch
implementation. This change:
- Adds pytorchWideDeepWorkload using the new pytorch-wide-deep image (1.0.0)
- Removes tfWideDeepWorkload and tf-wide-deep image references
- Enables arm64 support (PyTorch image is multi-arch)
- Uses the same log parsing (time -p output format)
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
The npb-is image was failing to build on ppc64le with relocation overflow:
relocation truncated to fit: R_PPC64_TOC16_HA against symbol 'key_array'
Remove ppc64le and s390x from supported architectures:
- The IS benchmark with CLASS=D has ~8GB data arrays that require special
compiler flags for non-x86 architectures
- ppc64le and s390x builds are difficult to test and maintain
- Keep amd64 and arm64 which are the primary node performance test targets
I don't think these arch(es) ever worked!
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
Updates the codebase to use the new glibc-dns-testing image which replaces
the deprecated jessie-dnsutils image.
This PR depends on the glibc-dns-testing image being available in the
registry (registry.k8s.io/e2e-test-images/glibc-dns-testing:2.0.0).
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
