vsphere-csi-driver

vsphere-csi-driver copied to clipboard

What this PR does / why we need it: This PR adds env parameter PV_TO_BACKINGDISKOBJECTID_INTERVAL_MINUTES to vsphere-csi-driver.yaml for pv to backingdiskobjectid mapping feature, so that we can manually set the interval.

Testing done: Precheck in progress:

Special notes for your reviewer:

Release note:

Add env parameter PV_TO_BACKINGDISKOBJECTID_INTERVAL_MINUTES to vsphere-csi-driver yaml.

Hi @xinyanw409. 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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: xinyanw409 To complete the pull request process, please assign xing-yang after the PR has been reviewed. You can assign the PR to them by writing /assign @xing-yang in a comment when ready.

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

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

/assign @xing-yang

/ok-to-test

The change looks fine. Please post CI results.

Started vanilla Block pipeline... Build Number: 1168

Block vanilla build status: FAILURE 
Stage before exit: testbed-deployment 

Started vanilla Block pipeline... Build Number: 1170

Block vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
JUnit report was created: /home/worker/workspace/Block-Vanilla/Results/1170/vsphere-csi-driver/tests/e2e/junit.xml

Ran 1 of 355 Specs in 431.389 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 354 Skipped
PASS

Ginkgo ran 1 suite in 8m20.492013192s
Test Suite Passed
--
JUnit report was created: /home/worker/workspace/Block-Vanilla/Results/1170/vsphere-csi-driver/tests/e2e/junit.xml

Ran 14 of 355 Specs in 5552.737 seconds
SUCCESS! -- 14 Passed | 0 Failed | 0 Pending | 341 Skipped
PASS

Ginkgo ran 1 suite in 1h32m50.045283211s
Test Suite Passed
--
/home/worker/workspace/Block-Vanilla/Results/1170/vsphere-csi-driver/tests/e2e/csi_cns_telemetry.go:181

Ran 42 of 355 Specs in 617.441 seconds
FAIL! -- 41 Passed | 1 Failed | 0 Pending | 313 Skipped


Ginkgo ran 1 suite in 10m38.978654628s
Test Suite Failed

Started Vanilla block pre-checkin pipeline... Build Number: 1028

Build ID: 1028
Block vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
JUnit report was created: /home/worker/workspace/csi-block-vanilla-pre-check-in/1028/vsphere-csi-driver/tests/e2e/junit.xml

Ran 1 of 355 Specs in 354.878 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 354 Skipped
PASS

Ginkgo ran 1 suite in 6m52.583945643s
Test Suite Passed
--
JUnit report was created: /home/worker/workspace/csi-block-vanilla-pre-check-in/1028/vsphere-csi-driver/tests/e2e/junit.xml

Ran 12 of 355 Specs in 4807.901 seconds
SUCCESS! -- 12 Passed | 0 Failed | 0 Pending | 343 Skipped
PASS

Ginkgo ran 1 suite in 1h20m21.026158749s
Test Suite Passed
--
/home/worker/workspace/csi-block-vanilla-pre-check-in/1028/vsphere-csi-driver/tests/e2e/csi_cns_telemetry_statefulsets.go:175

Ran 40 of 355 Specs in 1013.800 seconds
FAIL! -- 34 Passed | 6 Failed | 0 Pending | 315 Skipped


Ginkgo ran 1 suite in 17m10.094419488s
Test Suite Failed

Started Vanilla block pre-checkin pipeline... Build Number: 1035

Started vanilla Block pipeline... Build Number: 1182

Started Vanilla block pre-checkin pipeline... Build Number: 1049

Build ID: 1049
Block vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
JUnit report was created: /home/worker/workspace/csi-block-vanilla-pre-check-in/1049/vsphere-csi-driver/tests/e2e/junit.xml

Ran 1 of 358 Specs in 331.196 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 357 Skipped
PASS

Ginkgo ran 1 suite in 6m41.090262768s
Test Suite Passed
--
JUnit report was created: /home/worker/workspace/csi-block-vanilla-pre-check-in/1049/vsphere-csi-driver/tests/e2e/junit.xml

Ran 12 of 358 Specs in 4465.495 seconds
SUCCESS! -- 12 Passed | 0 Failed | 0 Pending | 346 Skipped
PASS

Ginkgo ran 1 suite in 1h14m41.194356353s
Test Suite Passed
--
/home/worker/workspace/csi-block-vanilla-pre-check-in/1049/vsphere-csi-driver/tests/e2e/svmotion_detached_volume.go:164

Ran 40 of 358 Specs in 870.862 seconds
FAIL! -- 38 Passed | 2 Failed | 0 Pending | 318 Skipped


Ginkgo ran 1 suite in 14m56.449141712s
Test Suite Failed

Started Vanilla block pre-checkin pipeline... Build Number: 1055

Build ID: 1055
Block vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
JUnit report was created: /home/worker/workspace/csi-block-vanilla-pre-check-in/1055/vsphere-csi-driver/tests/e2e/junit.xml

Ran 1 of 358 Specs in 359.376 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 357 Skipped
PASS

Ginkgo ran 1 suite in 6m50.169492651s
Test Suite Passed
--

Ran 12 of 358 Specs in 4514.297 seconds
FAIL! -- 11 Passed | 1 Failed | 0 Pending | 346 Skipped
--- FAIL: TestE2E (4514.45s)
FAIL

Ginkgo ran 1 suite in 1h15m28.699404035s
Test Suite Failed

Started Vanilla block pre-checkin pipeline... Build Number: 1056

Build ID: 1056
Block vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
JUnit report was created: /home/worker/workspace/csi-block-vanilla-pre-check-in/1056/vsphere-csi-driver/tests/e2e/junit.xml

Ran 1 of 358 Specs in 327.630 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 357 Skipped
PASS

Ginkgo ran 1 suite in 6m17.974549128s
Test Suite Passed
--

Ran 12 of 358 Specs in 4128.572 seconds
FAIL! -- 9 Passed | 3 Failed | 0 Pending | 346 Skipped
--- FAIL: TestE2E (4128.76s)
FAIL

Ginkgo ran 1 suite in 1h9m5.494229883s
Test Suite Failed

Started Vanilla block pre-checkin pipeline... Build Number: 1089

Build ID: 1089
Block vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
JUnit report was created: /home/worker/workspace/csi-block-vanilla-pre-check-in/1089/vsphere-csi-driver/tests/e2e/junit.xml

Ran 1 of 358 Specs in 427.698 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 357 Skipped
PASS

Ginkgo ran 1 suite in 8m2.764662069s
Test Suite Passed
--

Ran 12 of 358 Specs in 4820.824 seconds
FAIL! -- 11 Passed | 1 Failed | 0 Pending | 346 Skipped
--- FAIL: TestE2E (4820.95s)
FAIL

Ginkgo ran 1 suite in 1h20m35.700591437s
Test Suite Failed

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

This bot triages issues and 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 issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

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

This bot triages issues and 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 issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

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

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

/close

@k8s-triage-robot: Closed this PR.

In response to this:

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

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

/close

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.