-
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
Automated cherry pick of #105509: [test]: Fix PreferNominatedNode test #105665
Automated cherry pick of #105509: [test]: Fix PreferNominatedNode test #105665
Conversation
Once the node gets deleted, the nodelifecycle controller is racing to update pod status and the pod deletion logic is failing causing tests to flake. This commit moves the testContext creation to within the test loop and deletes nodes, namespace within the test loop. We don't explicitly call the node deletion within the loop but the `testutils.CleanupTest(t, testCtx)` call ensures that the namespace, nodes gets deleted.
@chendave: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cc @alculquicondor |
cc: @kubernetes/release-managers |
/lgtm |
/sig scheduling |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/kind failing-test
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alculquicondor, chendave, saschagrunert 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 |
Cherry pick of #105509 on release-1.21.
#105509: [test]: Fix PreferNominatedNode test
For details on the cherry pick process, see the cherry pick requests page.