[WIP]vsan stretch with CSI snapshot testcases

[Aishwarya-Hebbar]

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]

[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

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]

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

[svcbot-qecnsdp]

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

[svcbot-qecnsdp]

Build ID: 143
GC build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 

vm_service_vsan_stretch_cluster.go:27:1: missing import path


Ginkgo ran 1 suite in 347.801687ms

Test Suite Failed
make: Leaving directory `/home/worker/workspace/kai_vsan_stretch_tkg_precheckin/Results/143/vsphere-csi-driver`

[svcbot-qecnsdp]

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

[svcbot-qecnsdp]

Build ID: 144
GC build status: FAILURE 
Stage before exit: e2e-tests 

[svcbot-qecnsdp]

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

[svcbot-qecnsdp]

Build ID: 145
GC build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 888 Skipped
--- FAIL: TestE2E (606.08s)
FAIL

Ginkgo ran 1 suite in 11m6.642963464s

Test Suite Failed
make: Leaving directory `/home/worker/workspace/kai_vsan_stretch_tkg_precheckin/Results/145/vsphere-csi-driver`

[svcbot-qecnsdp]

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

[svcbot-qecnsdp]

Build ID: 146
GC build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 888 Skipped
--- FAIL: TestE2E (5950.32s)
FAIL

Ginkgo ran 1 suite in 1h40m6.371252136s

Test Suite Failed
make: Leaving directory `/home/worker/workspace/kai_vsan_stretch_tkg_precheckin/Results/146/vsphere-csi-driver`

[svcbot-qecnsdp]

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

[svcbot-qecnsdp]

Build ID: 147
GC build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 888 Skipped
--- FAIL: TestE2E (4815.86s)
FAIL

Ginkgo ran 1 suite in 1h21m26.05536814s

Test Suite Failed
make: Leaving directory `/home/worker/workspace/kai_vsan_stretch_tkg_precheckin/Results/147/vsphere-csi-driver`

[svcbot-qecnsdp]

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

[svcbot-qecnsdp]

Build ID: 148
GC build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 888 Skipped
--- FAIL: TestE2E (5135.97s)
FAIL

Ginkgo ran 1 suite in 1h26m41.718426711s

Test Suite Failed
make: Leaving directory `/home/worker/workspace/kai_vsan_stretch_tkg_precheckin/Results/148/vsphere-csi-driver`

[svcbot-qecnsdp]

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

[svcbot-qecnsdp]

Build ID: 159
GC build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 888 Skipped
--- FAIL: TestE2E (606.04s)
FAIL

Ginkgo ran 1 suite in 11m37.085726757s

Test Suite Failed
make: Leaving directory `/home/worker/workspace/kai_vsan_stretch_tkg_precheckin@2/Results/159/vsphere-csi-driver`

[svcbot-qecnsdp]

Build ID: 158
GC build status: FAILURE 
Stage before exit: e2e-tests 

[svcbot-qecnsdp]

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

[svcbot-qecnsdp]

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

[svcbot-qecnsdp]

Build ID: 161
GC build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 888 Skipped
--- FAIL: TestE2E (605.82s)
FAIL

Ginkgo ran 1 suite in 11m13.865438483s

Test Suite Failed
make: Leaving directory `/home/worker/workspace/kai_vsan_stretch_tkg_precheckin/Results/161/vsphere-csi-driver`

[svcbot-qecnsdp]

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

[svcbot-qecnsdp]

Build ID: 162
GC build status: FAILURE 
Stage before exit: e2e-tests 

[svcbot-qecnsdp]

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

[svcbot-qecnsdp]

Build ID: 163
GC build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 888 Skipped
--- FAIL: TestE2E (650.37s)
FAIL

Ginkgo ran 1 suite in 12m31.697674314s

Test Suite Failed
make: Leaving directory `/home/worker/workspace/kai_vsan_stretch_tkg_precheckin/Results/163/vsphere-csi-driver`

[svcbot-qecnsdp]

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

[svcbot-qecnsdp]

Build ID: 164
GC build status: FAILURE 
Stage before exit: e2e-tests 

[svcbot-qecnsdp]

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

[svcbot-qecnsdp]

Build ID: 165
GC build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 888 Skipped
--- FAIL: TestE2E (5575.33s)
FAIL

Ginkgo ran 1 suite in 1h34m28.979733739s

Test Suite Failed
make: Leaving directory `/home/worker/workspace/kai_vsan_stretch_tkg_precheckin/Results/165/vsphere-csi-driver`

[svcbot-qecnsdp]

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

[svcbot-qecnsdp]

Build ID: 166
GC build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 888 Skipped
--- FAIL: TestE2E (5458.42s)
FAIL

Ginkgo ran 1 suite in 1h32m8.659264861s

Test Suite Failed
make: Leaving directory `/home/worker/workspace/kai_vsan_stretch_tkg_precheckin/Results/166/vsphere-csi-driver`

[svcbot-qecnsdp]

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

[svcbot-qecnsdp]

Build ID: 167
GC build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 888 Skipped
--- FAIL: TestE2E (4.46s)
FAIL

Ginkgo ran 1 suite in 59.671483553s

Test Suite Failed
make: Leaving directory `/home/worker/workspace/kai_vsan_stretch_tkg_precheckin/Results/167/vsphere-csi-driver`

[svcbot-qecnsdp]

Build ID: 168
GC build status: FAILURE 
Stage before exit: checkout 

[svcbot-qecnsdp]

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

[svcbot-qecnsdp]

Build ID: 169
GC build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 888 Skipped
--- FAIL: TestE2E (5726.32s)
FAIL

Ginkgo ran 1 suite in 1h36m20.445319395s

Test Suite Failed
make: Leaving directory `/home/worker/workspace/kai_vsan_stretch_tkg_precheckin/Results/169/vsphere-csi-driver`

[svcbot-qecnsdp]

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

[svcbot-qecnsdp]

Build ID: 170
GC build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 888 Skipped
--- FAIL: TestE2E (3.02s)
FAIL

Ginkgo ran 1 suite in 1m15.462859129s

Test Suite Failed
make: Leaving directory `/home/worker/workspace/kai_vsan_stretch_tkg_precheckin/Results/170/vsphere-csi-driver`

[k8s-ci-robot]

PR needs rebase.

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-sigs/prow repository.