-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Update OCI Linux Resource Tests Failing (on a host w/o swap controller) #7918
Comments
It looks like a discussion on this was also started in pull request #7836 (#7836 (comment)). |
How do you run the test? It is passing on the CI (Ubuntu 20.04, Fedora 37, Rocky 8) |
This issue has been appearing for me while running |
On what environment? |
I have tested the same process on Ubuntu 20.04 on both Power ppc64le and x86 CPUs. |
@AkihiroSuda Looking at these lines: https://github.com/AkihiroSuda/containerd/blob/41575038819551c255ea2385dfe6c63cb7048dca/pkg/cri/opts/spec_linux.go#L484-L486 Since |
@AkihiroSuda I proposed a fix for this issue please let me know what do you think about it? |
Description
The TestUpdateOCILinuxResource tests are failing in pkg/cri/server and pkg/cri/sbserver. All tests fail due to the expected swap value not matching the received swap value.
These test cases were recently changed in pull request #7783, which disables swap by setting the value of the swap resource equal to the memory limit. Instead of the swap value being updated to match the expected value (the memory limit), in this case the swap value is left unchanged causing the test cases to fail (see test output below).
Steps to reproduce the issue
pkg/cri/server
orpkg/cri/sbserver
directoriesgo test -run TestUpdateOCILinuxResource
Describe the results you received and expected
Expected: All tests to pass
Received:
What version of containerd are you using?
containerd github.com/containerd/containerd v1.7.0-beta.1-121-g28e8e247b.m 28e8e24.m
Any other relevant information
No response
Show configuration if it is related to CRI plugin.
No response
The text was updated successfully, but these errors were encountered: