vsphere-csi-driver
vsphere-csi-driver copied to clipboard
kubernetes-sigs
TKG HA automation - PART 1
What this PR does / why we need it: TKG HA topology 3 testcases automation along with utils
Testing done: https://gist.github.com/Aishwarya-Hebbar/84799a00ec151203848b53e765e22784
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/test-infra repository.
Build ID: 122
GC build status: SUCCESS
Stage before exit: finally
Jenkins E2E Test Results:
Ran 1 of 621 Specs in 58.701 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 620 Skipped
PASS
Ginkgo ran 1 suite in 2m12.326728373s
Test Suite Passed
make: Leaving directory `/home/worker/workspace/kai-tkg-ha-gc/Results/122/vsphere-csi-driver`
Build ID: 123
GC build status: SUCCESS
Stage before exit: finally
Jenkins E2E Test Results:
Ran 1 of 621 Specs in 114.567 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 620 Skipped
PASS
Ginkgo ran 1 suite in 2m56.022400927s
Test Suite Passed
make: Leaving directory `/home/worker/workspace/kai-tkg-ha-gc/Results/123/vsphere-csi-driver`
Build ID: 124
GC build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 1 of 621 Specs in 29.848 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 620 Skipped
--- FAIL: TestE2E (30.07s)
FAIL
Ginkgo ran 1 suite in 1m34.521128723s
Test Suite Failed
make: Leaving directory `/home/worker/workspace/kai-tkg-ha-gc/Results/124/vsphere-csi-driver`
For all the new util methods which you have created for TKGS HA, those looks very similar to topology L5 util methods Can we try to use those same util methods instead of creating new one
Have addressed this by making the code generic and adding a flag.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Aishwarya-Hebbar, kavyashree-r, sipriyaa
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~tests/e2e/OWNERS~~ [kavyashree-r]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 24 of 621 Specs in 38.418 seconds
FAIL! -- 0 Passed | 24 Failed | 0 Pending | 597 Skipped
--- FAIL: TestE2E (38.67s)
FAIL
Ginkgo ran 1 suite in 2m11.960873555s
Test Suite Failed
Block vanilla build status: FAILURE
Stage before exit: e2e-tests
Jenkins E2E Test Results:
Ran 24 of 621 Specs in 4917.650 seconds
FAIL! -- 21 Passed | 3 Failed | 0 Pending | 597 Skipped
--- FAIL: TestE2E (4917.99s)
FAIL
Ginkgo ran 1 suite in 1h23m41.882371479s
Test Suite Failed