...
Z008
...
| https://cwiki.apache.org/confluence/pages/editpage.action?pageId=30150753# Test cases repeated for hypervisors & host versions: |
|
|
|
|
|
|
|
|
| ||
Test Case ID | Test Case Name |
| Expected Results | Priority | Test Case Type( Sanity | Functional | | Execution Time | Executed on Release | Reviewed By | Status | Comments | ||
HA001 | Host maintenance mode | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P1 | SANITY, FUNCTIONAL | 1 hour |
|
| pass |
| ||
HA002 | Host maintenance mode with activities | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P1 | SANITY, FUNCTIONAL | 1 hour |
|
| pass |
| Pass | Creating snapshot from ROOT volumes taking 4-5 minute time and for data volume it is faster(1-2 minute). |
HA003 | Network disconnect | HA003 | Network disconnect | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P1 | SANITY, FUNCTIONAL | 1 hour |
|
| pass |
|
HA004 | Network disconnect with activities | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P1 | SANITY, FUNCTIONAL | 1 hour |
|
| pass |
| ||
HA005 | Host power off (not a graceful shutdown) | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P1 | SANITY, FUNCTIONAL |
|
|
| Pass pass |
| ||
HA006 | Host power off with activities (not a graceful shutdown) | 1. Create Advance zone, pod, cluster. | 3. Deploy Vms on host 2 should succeed. All ongoing activities in step 3 should succeed. | P1 | SANITY, FUNCTIONAL | 1 hour |
|
| Pass pass |
| ||
Z007 HA007 | Host maintenance mode Maintenance mode with 2 hosts in cluster - Vms need not be HA enabled for being live migrated | 1. Have 1 host in 1 cluster. | After step4 - Check the following
|
...
Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P2 | SANITY, FUNCTIONAL | 1 hour |
|
| On Hold |
| ||
HA008 |
|
|
|
|
|
|
|
|
|
|
HA007 | Network disconnect |
|
...
...
Z009
...
Maintenance mode with 2 hosts in cluster with different host tag
...
...
1.Host1 should be put in maintenance mode successfully. All the Vms should remain in stopped state since they cannot live migrate to host2 which has no host tags.
...
P1
...
SANITY, FUNCTIONAL
...
1 hour
...
...
...
Pass
...
...
HA010
1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P2 | SANITY, FUNCTIONAL | 1 hour |
|
| hold |
| ||
|
|
|
|
|
|
|
|
|
|
|
HA008 | Host power off (not a graceful shutdown) | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P2 | SANITY, FUNCTIONAL |
|
|
| hold |
|
|
|
|
|
|
|
|
|
|
|
|
HA009 | Host maintenance mode | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P2 | SANITY, FUNCTIONAL | 1 hour |
|
| hold |
|
|
|
|
|
|
|
|
|
|
|
|
HA010 | Network disconnect | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P2 | SANITY, FUNCTIONAL | 1 hour |
|
| hold |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
HA011 | Host power off (not a graceful shutdown) | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P2 | SANITY, FUNCTIONAL |
|
|
| hold |
|
|
|
|
|
|
|
|
|
|
|
|
HA012 | Host maintenance mode | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P2 | SANITY, FUNCTIONAL | 1 hour |
|
| hold |
|
|
|
|
|
|
|
|
|
|
|
|
HA013 | Network disconnect | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P2 | SANITY, FUNCTIONAL | 1 hour |
|
| hold |
|
HA014 | Host power off (not a graceful shutdown) | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P2 | SANITY, FUNCTIONAL |
|
|
| hold |
|
HA015 | Host maintenance mode | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P1 | SANITY, FUNCTIONAL | 1 hour |
|
| pass |
|
HA016 | Network disconnect | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P1 | SANITY, FUNCTIONAL | 1 hour |
|
| pass |
|
HA017 | Host power off (graceful shutdown) | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P1 | SANITY, FUNCTIONAL |
|
|
| Failed |
|
HA018 | Host maintenance mode | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P2 | SANITY, FUNCTIONAL | 1 hour |
|
| hold |
|
HA019 | Network disconnect | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P2 | SANITY, FUNCTIONAL | 1 hour |
|
| hold |
|
HA020 | Host power off (not a graceful shutdown) | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P2 | SANITY, FUNCTIONAL |
|
|
| hold |
|
HA021 | Host maintenance mode | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P2 | SANITY, FUNCTIONAL | 1 hour |
|
| hold |
|
HA022 | Network disconnect | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P2 | SANITY, FUNCTIONAL | 1 hour |
|
| hold |
|
HA023 | Host power off (not a graceful shutdown) | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P2 | SANITY, FUNCTIONAL |
|
|
| hold |
|
HA024 | Host maintenance mode | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P1 | SANITY, FUNCTIONAL | 1 hour |
|
| pass |
|
HA025 | Network disconnect | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P1 | SANITY, FUNCTIONAL | 1 hour |
|
| Failed |
|
HA026 | Host power off (not a graceful shutdown) | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P1 | SANITY, FUNCTIONAL |
|
|
| Failed 15186 |
|
HA027 | Host maintenance mode |
...
1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P1 | SANITY, FUNCTIONAL | 1 hour |
|
|
...
Fail
...
Host resource stuck in "ErrorInMaintenance"
...
HA011
pass | NFS |
HA028 | Network disconnect |
|
...
vmware |
...
ESXi 5. |
...
0 |
...
ISCSI | 1. Create Advance zone, pod, cluster. |
...
. Create |
...
Vms. Acquire IP. Create port forwarding & load balancing rules for Vms. |
...
. |
...
Host 1 : Disconnect the NIC |
...
2 succeeds, deploy |
...
Vms | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. |
...
should succeed. | P1 | SANITY, FUNCTIONAL | 1 hour |
|
|
...
...
...
HA012
...
Failed | NFS | |
HA029 | Host power off (not a graceful shutdown) |
|
...
vmware |
...
ESXi 5. |
...
0 |
...
ISCSI | 1. Create Advance zone, pod, cluster. |
...
Create a custom compute service offering with HA. Create HA enabled Vms & Acquire IP. Create port forwarding & load balancing rules for Vms. |
...
Power off (not shutdown) | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. | P1 | SANITY, FUNCTIONAL |
...
|
|
|
...
Fail
...
HA013
...
Failed | NFS | |
HA030 | Host maintenance mode |
|
...
OVM |
...
2.3 |
...
ISCSI | 1. Create Advance zone, pod, cluster. |
...
Create port forwarding & load balancing rules for Vms. |
...
After failover to Host 2 succeeds, deploy Vms |
...
1 succeeds, deploy |
...
VMs | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. |
...
|
...
1 should succeed. |
...
P2 | SANITY, FUNCTIONAL | 1 hour |
|
|
...
Also, Sudha says to not do OVM. |
|
...
HA014
HA031 | Network disconnect |
|
...
OVM |
...
2.3 |
...
ISCSI | 1. Create Advance zone, pod, cluster. | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. |
...
P2 | SANITY, FUNCTIONAL | 1 hour |
|
|
...
|
|
...
HA032 | Host power off |
...
(not a graceful shutdown) |
...
OVM |
...
2.3 |
...
ISCSI | 1. Create Advance zone, pod, cluster. |
...
Host 1 : Power off (not shutdown) | 3. All Vms should failover to Host 2 in cluster. Vms should be in running state. |
...
. Deploy Vms on host 2 |
...
should succeed. |
...
P2 | SANITY, FUNCTIONAL |
...
|
|
|
...
Also, Sudha says to not do OVM. |
|
...
HA033 | Maintenance mode with 2 hosts in cluster - Vms need not be HA enabled for being live migrated |
...
1. Have 1 host in 1 cluster. | After step4 - Check the following
|
...
|
|
|
|
| pass |
| |
HA034 |
...
Maintenance mode with 1 host in cluster |
...
|
...
|
...
Verity following after step3. |
...
|
|
|
|
| pass |
| |
HA035 |
...
Maintenance mode with 2 hosts in cluster with different host tag |
...
...
| 1.Host1 should be put in maintenance mode successfully. All the Vms should remain in stopped state since they cannot live migrate to host2 which has no host tags. |
...
|
...
SANITY, FUNCTIONAL
|
|
...
|
|
...
Fail |