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

tag ginkgo tests affected by pdcsi migration for skipping #105052

Merged
merged 1 commit into from
Oct 11, 2021

Conversation

leiyiz
Copy link
Contributor

@leiyiz leiyiz commented Sep 15, 2021

What type of PR is this?

What this PR does / why we need it:

When we turn on CSIMigrationGCE, some prow tests (and unit tests) are going to fail due to their reliance on gcepd driver. we need to tag them with an appropriate tag so that we can skip them in release-blocking jobs and presubmits.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. 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. labels Sep 15, 2021
@k8s-ci-robot
Copy link
Contributor

Hi @leiyiz. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@k8s-ci-robot k8s-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. area/test sig/apps Categorizes an issue or PR as relevant to SIG Apps. labels Sep 15, 2021
@k8s-ci-robot k8s-ci-robot added sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/testing Categorizes an issue or PR as relevant to SIG Testing. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Sep 15, 2021
@leiyiz
Copy link
Contributor Author

leiyiz commented Sep 15, 2021

@mattcary
@msau42
@jpbetz

@mattcary
Copy link
Contributor

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Sep 15, 2021
@leiyiz
Copy link
Contributor Author

leiyiz commented Sep 15, 2021

/retest

@SergeyKanzhelev SergeyKanzhelev moved this from Triage to PRs - Needs Reviewer in SIG Node CI/Test Board Sep 16, 2021
@ehashman ehashman added this to Triage in SIG Node PR Triage Sep 20, 2021
@MadhavJivrajani
Copy link
Contributor

/priority important-soon
/kind cleanup
/triage accepted

@k8s-ci-robot k8s-ci-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Sep 20, 2021
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. sig/storage Categorizes an issue or PR as relevant to SIG Storage. labels Sep 30, 2021
@k8s-ci-robot k8s-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Sep 30, 2021
@leiyiz leiyiz requested a review from msau42 October 1, 2021 18:43
test/e2e/cloud/gcp/cluster_upgrade.go Outdated Show resolved Hide resolved
@@ -43,7 +43,7 @@ import (
"k8s.io/kubernetes/test/e2e/storage/utils"
)

var _ = utils.SIGDescribe("Mounted volume expand", func() {
var _ = utils.SIGDescribe("Mounted volume expand [Feature:StorageProviderGCEPD]", func() {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

@leiyiz leiyiz Oct 1, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, what I mean is are these tests in mounted_volume_resize still needed or do we have equivalent test cases in testsuites/volume_expand.go

Copy link
Contributor Author

@leiyiz leiyiz Oct 4, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this test in mounted_volume_resize will also run due to focus [V|v]olume\sexpand

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This e2e exercises a test which is not covered by test suite. I think we had some bug where if while volume is mounted and you quickly deleted the pod and recreated it (where global mount does not have chance to be removed), resize won't work. This e2e exercises that scenario.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking at this test case, I don't see anything that prevents the test from being imported into testsuites/volume_expand.go. Can you file a bug to track moving this test over? For now I think adding the tag to it is fine, but we'll want to move the test and remove the tag before 1.23 code freeze.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no problem. #105581

test/e2e/storage/pd.go Outdated Show resolved Hide resolved
test/e2e/storage/persistent_volumes.go Outdated Show resolved Hide resolved
test/e2e/storage/persistent_volumes.go Outdated Show resolved Hide resolved
@leiyiz leiyiz force-pushed the skip-storage-test branch 3 times, most recently from 8d84abe to d919128 Compare October 8, 2021 18:29
@msau42
Copy link
Member

msau42 commented Oct 8, 2021

Can you also open an issue to track the upgrade test issue?

@msau42
Copy link
Member

msau42 commented Oct 8, 2021

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: leiyiz, msau42

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 Oct 8, 2021
…rageclass check for statefulset and upgrade tests
@leiyiz
Copy link
Contributor Author

leiyiz commented Oct 11, 2021

Can you also open an issue to track the upgrade test issue?

no problem #105595

@mattcary
Copy link
Contributor

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 11, 2021
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Oct 11, 2021

@leiyiz: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-kubernetes-node-kubelet-serial b6943f87915fe1c9fb4427db75b7f70eae2e065d link /test pull-kubernetes-node-kubelet-serial
pull-kubernetes-node-kubelet-serial-containerd b6943f87915fe1c9fb4427db75b7f70eae2e065d link /test pull-kubernetes-node-kubelet-serial-containerd

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.

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. I understand the commands that are listed here.

@leiyiz
Copy link
Contributor Author

leiyiz commented Oct 11, 2021

/retest

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. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. 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/apps Categorizes an issue or PR as relevant to SIG Apps. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/storage Categorizes an issue or PR as relevant to SIG Storage. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Archived in project
Archived in project
SIG Node PR Triage
Needs Reviewer
Development

Successfully merging this pull request may close these issues.

None yet

8 participants