Skip to content
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

Merged
merged 4 commits into from
Nov 9, 2021

Conversation

ffromani
Copy link
Contributor

@ffromani ffromani commented Nov 3, 2021

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?

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Nov 3, 2021
@ffromani
Copy link
Contributor Author

ffromani commented Nov 3, 2021

/sig node
suggested priority: important-longterm (because the fix is trivial)

@k8s-ci-robot k8s-ci-robot added sig/node Categorizes an issue or PR as relevant to SIG Node. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Nov 3, 2021
@ffromani
Copy link
Contributor Author

ffromani commented Nov 3, 2021

/cc @cynepco3hahue @swatisehgal

@k8s-ci-robot k8s-ci-robot added area/test sig/testing Categorizes an issue or PR as relevant to SIG Testing. labels Nov 3, 2021
@ffromani ffromani changed the title E2e podresources fix E2E podresources: fix test checking esclusive cpus allocation Nov 3, 2021
@ffromani
Copy link
Contributor Author

ffromani commented Nov 3, 2021

/hold
running final tests on the aforementioned BM

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 3, 2021
@SergeyKanzhelev SergeyKanzhelev moved this from Triage to PRs - Needs Reviewer in SIG Node CI/Test Board Nov 3, 2021
@SergeyKanzhelev
Copy link
Member

/assign @cynepco3hahue
/triage accepted
/priority important-soon

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Nov 3, 2021
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 8, 2021
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 8, 2021
@SergeyKanzhelev
Copy link
Member

/hold running final tests on the aforementioned BM

@fromanirh do you still need this hold?

@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 8, 2021
@ffromani
Copy link
Contributor Author

ffromani commented Nov 9, 2021

/hold running final tests on the aforementioned BM

@fromanirh do you still need this hold?

yes, but I plan to lift it soon as the last internal verification is in progress (pending BM availability)

@ffromani
Copy link
Contributor Author

ffromani commented Nov 9, 2021

BM tests revealed an additional issue with kubelet restart. Investigating. Will keep updating.

@ffromani
Copy link
Contributor Author

ffromani commented Nov 9, 2021

ok, restarting the kubelet in the e2e tests seems to be broken. I'll investigate.

@cynepco3hahue
Copy link

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>
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>
@ffromani ffromani force-pushed the e2e-podresources-fix branch 3 times, most recently from b850f44 to a1c10da Compare November 9, 2021 17:49
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>
@ffromani
Copy link
Contributor Author

ffromani commented Nov 9, 2021

Our BM tests is green again; we managed to provide a couple extra fixes. Kudos to @cynepco3hahue for helping here!

@cynepco3hahue
Copy link

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 9, 2021
@ehashman
Copy link
Member

ehashman commented Nov 9, 2021

/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 9, 2021
@k8s-ci-robot k8s-ci-robot merged commit e4adf7f into kubernetes:master Nov 9, 2021
SIG Node CI/Test Board automation moved this from PRs - Needs Reviewer to Done Nov 9, 2021
@k8s-ci-robot k8s-ci-robot added this to the v1.23 milestone Nov 9, 2021
@ffromani ffromani deleted the e2e-podresources-fix branch November 10, 2021 06:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/test cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. release-note-none Denotes a PR that doesn't merit a release note. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

None yet

6 participants