search

kubernetes-sigs / vsphere-csi-driver

vSphere storage Container Storage Interface (CSI) plugin
https://docs.vmware.com/en/VMware-vSphere-Container-Storage-Plug-in/index.html
Apache License 2.0
296 stars 179 forks source link

[WIP]Overcome resource quota issue hack #2859

Closed Aishwarya-Hebbar closed 2 weeks ago

Aishwarya-Hebbar commented 5 months ago

What this PR does / why we need it:

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Testing done: A PR must be marked "[WIP]", if no test result is provided. A WIP PR won't be reviewed, nor merged. The requester can determine a sufficient test, e.g. build for a cosmetic change, E2E test in a predeployed setup, etc. For new features, new tests should be done, in addition to regression tests. If jtest is used to trigger precheckin tests, paste the result after jtest completes and remove [WIP] in the PR subject. The review cycle will start, only after "[WIP]" is removed from the PR subject.

Special notes for your reviewer:

Release note:

k8s-ci-robot commented 5 months ago

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Aishwarya-Hebbar Once this PR has been reviewed and has the lgtm label, please assign kavyashree-r for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files: - **[tests/e2e/OWNERS](https://github.com/kubernetes-sigs/vsphere-csi-driver/blob/master/tests/e2e/OWNERS)** 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 commented 5 months ago

Hi @Aishwarya-Hebbar. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
svcbot-qecnsdp commented 5 months ago

Started GC block pre-checkin pipeline... Build Number: 191

svcbot-qecnsdp commented 5 months ago 
Build ID: 191
GC build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
FAIL! -- 0 Passed | 6 Failed | 0 Pending | 842 Skipped
--- FAIL: TestE2E (563.36s)
FAIL

Ginkgo ran 1 suite in 11m6.891791737s

Test Suite Failed
make: Leaving directory `/home/worker/workspace/kai_gc_csi_precheckin/Results/191/vsphere-csi-driver`
svcbot-qecnsdp commented 5 months ago

Started GC block pre-checkin pipeline... Build Number: 193

svcbot-qecnsdp commented 5 months ago 
Build ID: 193
GC build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
FAIL! -- 0 Passed | 6 Failed | 0 Pending | 842 Skipped
--- FAIL: TestE2E (450.92s)
FAIL

Ginkgo ran 1 suite in 9m0.649096411s

Test Suite Failed
make: Leaving directory `/home/worker/workspace/kai_gc_csi_precheckin/Results/193/vsphere-csi-driver`
svcbot-qecnsdp commented 5 months ago

Started GC block pre-checkin pipeline... Build Number: 194

svcbot-qecnsdp commented 5 months ago 
Build ID: 194
GC build status: FAILURE 
Stage before exit: e2e-tests
svcbot-qecnsdp commented 5 months ago

Started GC block pre-checkin pipeline... Build Number: 195

svcbot-qecnsdp commented 5 months ago 
Build ID: 195
GC build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
FAIL! -- 0 Passed | 6 Failed | 0 Pending | 842 Skipped
--- FAIL: TestE2E (22.85s)
FAIL

Ginkgo ran 1 suite in 2m32.446160113s

Test Suite Failed
make: Leaving directory `/home/worker/workspace/kai_gc_csi_precheckin/Results/195/vsphere-csi-driver`
svcbot-qecnsdp commented 5 months ago

Started GC block pre-checkin pipeline... Build Number: 196

svcbot-qecnsdp commented 5 months ago 
Build ID: 196
GC build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
FAIL! -- 0 Passed | 6 Failed | 0 Pending | 842 Skipped
--- FAIL: TestE2E (24.04s)
FAIL

Ginkgo ran 1 suite in 2m33.875569682s

Test Suite Failed
make: Leaving directory `/home/worker/workspace/kai_gc_csi_precheckin/Results/196/vsphere-csi-driver`
svcbot-qecnsdp commented 5 months ago

Started GC block pre-checkin pipeline... Build Number: 197

svcbot-qecnsdp commented 5 months ago 
Build ID: 197
GC build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
FAIL! -- 0 Passed | 6 Failed | 0 Pending | 842 Skipped
--- FAIL: TestE2E (2280.07s)
FAIL

Ginkgo ran 1 suite in 39m49.614092441s

Test Suite Failed
make: Leaving directory `/home/worker/workspace/kai_gc_csi_precheckin/Results/197/vsphere-csi-driver`
k8s-triage-robot commented 2 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 month ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 2 weeks ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

k8s-ci-robot commented 2 weeks ago

@k8s-triage-robot: Closed this PR.

In response to [this](https://github.com/kubernetes-sigs/vsphere-csi-driver/pull/2859#issuecomment-2359251493): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages PRs according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the PR is closed > >You can: >- Reopen this PR with `/reopen` >- Mark this PR as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.