vsphere-csi-driver
vsphere-csi-driver copied to clipboard
kubernetes-sigs
Add validation to check compatible datastore accessible from all vms
What this PR does / why we need it: pr will add validation to check if compatible datastores are accessible from all vm nodes.
Testing done: Manually Tested Running E2E pipeline
Special notes for your reviewer: logs for manual testing: logs-non-compatible-ds.TXT
Release note:
adding validation while creating volumes to check if compatible datastores are accessible from all vm nodes.
Hi @nikhilbarge. 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: nikhilbarge
Once this PR has been reviewed and has the lgtm label, please assign shalini-b for approval by writing /assign @shalini-b in a comment. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Build ID: 1525
Block vanilla build status: SUCCESS
Stage before exit: e2e-tests
Jenkins E2E Test Results:
------------------------------
Ran 1 of 678 Specs in 349.209 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 677 Skipped
PASS
Ginkgo ran 1 suite in 13m14.365161256s
Test Suite Passed
--
------------------------------
Ran 12 of 678 Specs in 4376.320 seconds
SUCCESS! -- 12 Passed | 0 Failed | 0 Pending | 666 Skipped
PASS
Ginkgo ran 1 suite in 1h13m54.077187937s
Test Suite Passed
--
------------------------------
Ran 40 of 678 Specs in 5025.554 seconds
SUCCESS! -- 40 Passed | 0 Failed | 0 Pending | 638 Skipped
PASS
Ginkgo ran 1 suite in 1h24m54.309121378s
Test Suite Passed
Block vanilla build status: FAILURE
Stage before exit: testbed-deployment
Build ID: 1533
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
------------------------------
Ran 1 of 678 Specs in 350.780 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 677 Skipped
PASS
Ginkgo ran 1 suite in 13m24.099472405s
Test Suite Passed
--
Ran 12 of 678 Specs in 3415.934 seconds
FAIL! -- 3 Passed | 9 Failed | 0 Pending | 666 Skipped
--- FAIL: TestE2E (3415.97s)
FAIL
Ginkgo ran 1 suite in 57m52.543687071s
Test Suite Failed
Block vanilla build status: FAILURE
Stage before exit: testbed-deployment
Block vanilla build status: FAILURE
Stage before exit: testbed-deployment
Block vanilla build status: FAILURE
Stage before exit: testbed-deployment
VCP to CSI migration build status: SUCCESS
Stage before exit: finally
Jenkins E2E Test Results:
------------------------------
Ran 18 of 678 Specs in 5773.740 seconds
SUCCESS! -- 18 Passed | 0 Failed | 0 Pending | 660 Skipped
PASS
Ginkgo ran 1 suite in 1h37m16.469370877s
Test Suite Passed
Block vanilla build status: SUCCESS
Stage before exit: finally
Jenkins E2E Test Results:
------------------------------
Ran 24 of 687 Specs in 4047.237 seconds
SUCCESS! -- 24 Passed | 0 Failed | 0 Pending | 663 Skipped
PASS
Ginkgo ran 1 suite in 1h8m28.07860539s
Test Suite Passed