-
Notifications
You must be signed in to change notification settings - Fork 2.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
Enable e2e test for Alpha Feature AnyVolumeDataSource #25709
Enable e2e test for Alpha Feature AnyVolumeDataSource #25709
Conversation
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
/assign @cheftako Could you approve this PR? |
@@ -423,7 +423,7 @@ presubmits: | |||
- --provider=gce | |||
- --runtime-config=api/all=true | |||
- --stage=gs://kubernetes-release-pull/ci/pull-kubernetes-e2e-gce-alpha-features | |||
- --test_args=--ginkgo.focus=\[Feature:(GRPCContainerProbe|InPlacePodVerticalScaling|ProbeTerminationGracePeriod|APIServerTracing|StorageVersionAPI|PodPreset|StatefulSetMinReadySeconds|CustomResourceValidationExpressions)\]|Networking --ginkgo.skip=\[Feature:(SCTPConnectivity|Volumes|Networking-Performance)\]|IPv6|csi-hostpath-v0 --minStartupPods=8 | |||
- --test_args=--ginkgo.focus=\[Feature:(GRPCContainerProbe|InPlacePodVerticalScaling|ProbeTerminationGracePeriod|APIServerTracing|StorageVersionAPI|PodPreset|StatefulSetMinReadySeconds|CustomResourceValidationExpressions|AnyVolumeDataSource)\]|Networking --ginkgo.skip=\[Feature:(SCTPConnectivity|Volumes|Networking-Performance)\]|IPv6|csi-hostpath-v0 --minStartupPods=8 |
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.
Is there a Kubernetes PR validating that this test passes?
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.
Ah, I see kubernetes/kubernetes#108664, but do you know if this test ran? I think there's a way to configure a Kubernetes PR to run with a prow config from a PR, but I can't recall the details.
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.
@andrewsykim Thank you for your review. IIUC, without --ginkgo.focus
option for "[Feature:AnyVolumeDataSource]"
, the e2e tests containing "[Feature:AnyVolumeDataSource]"
string are skipped. So, this PR is needed to make this job not to skip these tests. In the PR, the job is enabled with /test pull-kubernetes-e2e-gce-alpha-features
, but the tests seem to be skipped.
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.
This is kind of hacky, but could you temporary update the ginkgo tag in your PR to something else to have the test run and see if it passes?
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.
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.
I'm not disagreeing with the approach to enable the tests, just asking if we can have a successful run of the test before enabling this for all alpha jobs. The (hacky) approach I mentioned is just a temporary hack to run the test in presubmit by using a known filter that works (just pick any of the existing alpha filters that are used).
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.
The test's PR is tested manually like this. The test requires alpha features, or AnyVolumeDataSource feature gate, to be enabled, which means removing [Feature:AnyVolumeDataSource]
will make this test run in other jobs which don't enable the feature gate and fail.
So, I will update the test's PR if it is really required before merging this PR, however, I don't think that it should be a blocker for this PR (This PR could be merged without any side effects and the test's PR can be merged later without any dependencies).
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.
The test's PR is tested manually like kubernetes/kubernetes#108664 (comment). The test requires alpha features, or AnyVolumeDataSource feature gate, to be enabled, which means removing [Feature:AnyVolumeDataSource] will make this test run in other jobs which don't enable the feature gate and fail.
This seems sufficient, thanks
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.
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andrewsykim, bswartz, mkimuram 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 |
@mkimuram: Updated the
In 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/test-infra repository. |
This PR enables e2e test for Alpha Feature AnyVolumeDataSource in job pull-kubernetes-e2e-gce-alpha-features.
xref: kubernetes/kubernetes#108664
/sig storage
@bswartz @xing-yang