Fix for k8s nfs related tests probably caused by ulimit changes
#9799
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
If this does not work, will file a revert for sure! |
|
GOOD: BAD: |
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
dims
force-pushed
the
fix-for-k8s-nfs-related-tests
branch
from
3324383
to
23ebfd0
Compare
MikeZappa87
approved these changes
Feb 10, 2024
mxpv
approved these changes
Feb 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
on 2/7 the k8s upstream jobs picked up a new version of ubuntu kernel and some of the NFS related jobs started failing:
We had the same issue with
kopsbased tests as well which we fixed by settingLimitNOFILEexplicitly to a known previous value:kubernetes/kops#16329
So we want to see if fixing this in the install scripts for the CI jobs works for us. Also note the pending PR here:
#9660
and the note back from 2019:
#3201 (comment)