-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
E2E podresources: fix test checking esclusive cpus allocation #106116
Conversation
/sig node |
/hold |
7cfb055
to
6102b7e
Compare
/assign @cynepco3hahue |
6102b7e
to
94e6fea
Compare
@fromanirh do you still need this hold? |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fromanirh, SergeyKanzhelev The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
yes, but I plan to lift it soon as the last internal verification is in progress (pending BM availability) |
BM tests revealed an additional issue with kubelet restart. Investigating. Will keep updating. |
ok, restarting the kubelet in the e2e tests seems to be broken. I'll investigate. |
Can be related to recent PRs related to DynamicKubeletConfguration removal. I will re-check the code. |
the intent is to make the code more readable, no intended changes in behaviour. Now it should be a bit more explicit why the code is checking some values. Signed-off-by: Francesco Romani <fromani@redhat.com>
Since commit 42dd01a the cpuRequest is in millicores, hence we need to properly check translating to exclusive cpus when verifying the resource allocation. Signed-off-by: Francesco Romani <fromani@redhat.com>
94e6fea
to
4b46c3a
Compare
we need to make sure the system state is completely cleaned up again, to avoid to mess up with the shared node state, before we transition from one test to another. Signed-off-by: Francesco Romani <fromani@redhat.com>
b850f44
to
a1c10da
Compare
Let's wait for the local node (aka the kubelet) to be ready before to query podresources again, to avoid false negatives. Co-authored-by: Artyom Lukianov <alukiano@redhat.com> Signed-off-by: Francesco Romani <fromani@redhat.com>
a1c10da
to
bf9bab5
Compare
Our BM tests is green again; we managed to provide a couple extra fixes. Kudos to @cynepco3hahue for helping here! |
/lgtm |
/hold cancel |
What type of PR is this?
/kind cleanup
/kind failing-test
What this PR does / why we need it:
Since commit 42dd01a the cpuRequest is in millicores, hence we need to properly check translating to exclusive cpus when verifying the resource allocation.
Which issue(s) this PR fixes:
Fixes N/A
Special notes for your reviewer:
This issue is not evident in our CI because the machines on which CI runs don't have enough cpus to perform exclusive allocations, hence the e2e tests skips. We figured out thanks to RH's internal testing on BM.
Does this PR introduce a user-facing change?