-
Notifications
You must be signed in to change notification settings - Fork 42.1k
fix flaky behavior due to the test ordering between DynamicProvisioner and Retroactive StorageClass Assignment #128905
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
Conversation
…r and Retroactive StorageClass Assignment
|
Skipping CI for Draft Pull Request. |
|
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 DetailsInstructions 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-sigs/prow repository. |
|
And thank @rifelpet a lot for finding the root casue. |
|
unrelated failures |
|
/test ? |
|
@carlory: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
DetailsIn response to this:
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-sigs/prow repository. |
|
/test pull-kubernetes-e2e-gce-serial |
|
/lgtm |
|
LGTM label has been added. DetailsGit tree hash: 7fd7e165d2d690e2544b80cd4466242a18c88685 |
|
/assign @xing-yang @msau42 |
|
/priority important-soon |
|
/lgtm |
|
/test pull-kubernetes-e2e-gce-serial |
1 similar comment
|
/test pull-kubernetes-e2e-gce-serial |
|
pull-kubernetes-e2e-gce-serial job failure is not related to this PR. /skip pull-kubernetes-e2e-gce-serial |
|
/retest |
|
/cc @jsafrane |
|
/cc @pohly |
|
I lack context here. Without a thorough description of the problem and why this change fixes that problem I cannot review this PR. |
|
@pohly sorry for the inconvenience. I have updated the PR's description. Please review it again. Thank you. |
|
/approve |
pohly
left a comment
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.
/lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: carlory, jsafrane, pohly The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
|
@carlory: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
What type of PR is this?
/kind flake
https://storage.googleapis.com/k8s-triage/index.html?test=Retroactive%20StorageClass%20Assignment%20should%20assign%20default%20StorageClass%20to%20PVCs%20retroactively
What this PR does / why we need it:
See #128849 (comment)
Test 1:
DynamicProvisionerTest 2:
Retroactive StorageClass AssignmentThe
updateDefaultStorageClassfunction setsstorageclass.beta.kubernetes.io/is-default-classandstorageclass.kubernetes.io/is-default-classannotations on the StorageClass. but thesetStorageClassDefaultfunction only setsstorageclass.kubernetes.io/is-default-classannotation. Even thoughstorageclass.beta.kubernetes.io/is-default-classis deprecated, it is still working in the cluster. so there is a flaky test failure in theRetroactive StorageClass Assignmenttest when it is excuted afterDynamicProvisionertest.In order to fix this issue, we need to replace the
setStorageClassDefaultfunction withupdateDefaultStorageClassfunction in theRetroactive StorageClass Assignmenttest.Which issue(s) this PR fixes:
Fixes #128849
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: