c81e99d98d
Automatic merge from submit-queue (batch tested with PRs 41728, 42231) Adding new tests to e2e/vsphere_volume_placement.go **What this PR does / why we need it**: Adding new tests to e2e/vsphere_volume_placement.go Below is the tests description and test steps. **Test Back-to-back pod creation/deletion with different volume sources on the same worker node** 1. Create volumes - vmdk2, vmdk1 is created in the test setup. 2. Create pod Spec - pod-SpecA with volume path of vmdk1 and NodeSelector set to label assigned to node1. 3. Create pod Spec - pod-SpecB with volume path of vmdk2 and NodeSelector set to label assigned to node1. 4. Create pod-A using pod-SpecA and wait for pod to become ready. 5. Create pod-B using pod-SpecB and wait for POD to become ready. 6. Verify volumes are attached to the node. 7. Create empty file on the volume to make sure volume is accessible. (Perform this step on pod-A and pod-B) 8. Verify file created in step 5 is present on the volume. (perform this step on pod-A and pod-B) 9. Delete pod-A and pod-B 10. Repeatedly (5 times) perform step 4 to 9 and verify associated volume's content is matching. 11. Wait for vmdk1 and vmdk2 to be detached from node. 12. Delete vmdk1 and vmdk2 **Test multiple volumes from different datastore within the same pod** 1. Create volumes - vmdk2 on non default shared datastore. 2. Create pod Spec with volume path of vmdk1 (vmdk1 is created in test setup on default datastore) and vmdk2. 3. Create pod using spec created in step-2 and wait for pod to become ready. 4. Verify both volumes are attached to the node on which pod are created. Write some data to make sure volume are accessible. 5. Delete pod. 6. Wait for vmdk1 and vmdk2 to be detached from node. 7. Create pod using spec created in step-2 and wait for pod to become ready. 8. Verify both volumes are attached to the node on which PODs are created. Verify volume contents are matching with the content written in step 4. 9. Delete POD. 10. Wait for vmdk1 and vmdk2 to be detached from node. 11. Delete vmdk1 and vmdk2 **Test multiple volumes from same datastore within the same pod** 1. Create volumes - vmdk2, vmdk1 is created in testsetup 2. Create pod Spec with volume path of vmdk1 (vmdk1 is created in test setup) and vmdk2. 3. Create pod using spec created in step-2 and wait for pod to become ready. 4. Verify both volumes are attached to the node on which pod are created. Write some data to make sure volume are accessible. 5. Delete pod. 6. Wait for vmdk1 and vmdk2 to be detached from node. 7. Create pod using spec created in step-2 and wait for pod to become ready. 8. Verify both volumes are attached to the node on which PODs are created. Verify volume contents are matching with the content written in step 4. 9. Delete POD. 10. Wait for vmdk1 and vmdk2 to be detached from node. 11. Delete vmdk1 and vmdk2 **Which issue this PR fixes** fixes # **Special notes for your reviewer**: Executed tests against K8S v1.5.3 release **Release note**: ```release-note NONE ``` cc: @kerneltime @abrarshivani @BaluDontu @tusharnt @pdhamdhere |
||
|---|---|---|
| .. | ||
| e2e | ||
| e2e_federation | ||
| e2e_node | ||
| fixtures | ||
| images | ||
| integration | ||
| kubemark | ||
| list | ||
| soak | ||
| utils | ||
| BUILD | ||
| OWNERS | ||
| test_owners.csv | ||