Test ID | Test Case Name | Steps To Be Performed to Test | Verification Steps | RHEL6.2 | RHEL 6.3 | RHEL6.4 | RHEL6.5 |
---|
| | | | | | | |
SP001 | Take snapshot on root disk of a Linux VM | - Deploy a Linux VM using default CentOS template, use small service offering, disk offering
- Log into the VM and create a file with content in it.
- Perform snapshot on the root disk of this newly created VM
| - Verify the snapshot's entry in the "snapshots" table.
- Verify the presence of the corresponding snapshot on the Secondary Storage
| https://issues.citrite.net/browse/CS-20692 not support RHEL 6.2 after CPP 4.4 release per discuss, as RHEl 6.2 doesn't support Java 7. | http://bugs-ccp.citrix.com/browse/CS-20737 blocked blocker work around PASS | https://issues.citrite.net/browse/CS-20737 blocked blocker work around PASS | https://issues.citrite.net/browse/CS-20737 blocked blocker work around PASS |
SP002 | Take snapshot on root disk of a Windows VM. | - Register/Create a Windows Template onto the CloudStack Setup.
- Deploy a Windows VM using the Windows template, use medium service offering, disk offering
- Log into the VM and create a file on the desktop with content in it.
- Perform snapshot on the root disk of this newly created VM
| - Verify the snapshot's entry in the "snapshots" table.
- Verify the presence of the corresponding snapshot on the Secondary Storage
| | http://bugs-ccp.citrix.com/browse/CS-20737 blocked blocker work around PASS | http://bugs-ccp.citrix.com/browse/CS-20737 blocked blocker work around PASS | http://bugs-ccp.citrix.com/browse/CS-20737 blocked blocker work around PASS |
SP003 | Take snapshot on data disk of a Linux VM. | - Deploy a Linux VM using default CentOS template, use small service offering, disk offering.
- Log into the VM and create a ext3 file system on the Data Disk.
- Mount the Data Disk.
- Create a File with content
on the Data Disk - Perform snapshot on the data disk of this newly created VM
| - Verify the snapshot's entry in the "snapshots" table.
- Verify the presence of the corresponding snapshot on the Secondary Storage
| | http://bugs-ccp.citrix.com/browse/CS-20737 blocked blocker work around PASS | http://bugs-ccp.citrix.com/browse/CS-20737 blocked blocker work around PASS | http://bugs-ccp.citrix.com/browse/CS-20737 blocked blocker work around PASS |
SP004 | Take snapshot on data disk of a Windows VM. | Steps need to be provided. | - Verify the snapshot's entry in the "snapshots" table.
- Verify the presence of the corresponding snapshot on the Secondary Storage
| | http://bugs-ccp.citrix.com/browse/CS-20737 blocked blocker work around PASS | http://bugs-ccp.citrix.com/browse/CS-20737 blocked blocker work around PASS | http://bugs-ccp.citrix.com/browse/CS-20737 blocked blocker work around PASS |
SP005 | Event Generation during Snapshot Creation | - Create a Snapshot.
- Observe the events table for the corresponding "SNAPSHOT.CREATE" event.
- Steps need to be provided.
| - Observe the events table for the corresponding "SNAPSHOT.CREATE" event.
| | PASS | PASS | PASS |
SP006 | Event Generation during Snapshot Deletion | - Delete a Snapshot.
- Observe the events table for the corresponding "SNAPSHOT.DELETE" event.
- Steps need to be provided.
| - Observe the events table for the corresponding "SNAPSHOT.DELETE" event.
| | PASS | PASS | PASS |
SP007 | Create Template from a Snapshot of a ROOT disk of a Linux VM. | - Create a Snapshot of a ROOT Volume of a Linux VM.
- Create a Template from the Snapshot with the appropriate Guest_os_type selected.
| - Verify the template's entry in the "template_host_ref" table.
- Verify the presence of the corresponding template on the Secondary Storage
| | PASS | PASS | PASS |
SP008 | Create Template from a Snapshot of a ROOT disk of a Windows VM. | - Create a Snapshot of a ROOT Volume of a Linux VM.
- Create a Template from the Snapshot with the appropriate Guest_os_type selected
| - Verify the template's entry in the "template_host_ref" table.
- Verify the presence of the corresponding template on the Secondary Storage
| | PASS | PASS | PASS |
SP009 | Deploy a Linux VM from the Template created from the Snapshot | - Deploy a VM using the Linux Template created from the Snapshot of a ROOT Volume of a Linux VM.
- Log in and check the operational ability of the VM.
| - Verify the Successful deployment of the VM.
- Log in and check the operational ability of the VM.
| | PASS | PASS | PASS |
SP010 | Deploy a Windows VM from the Template created from the Snapshot | - Deploy a VM using the Windows Template created from the Snapshot of a ROOT Volume of a Windows VM.
- Log in and check the operational ability of the VM.
| - Verify the Successful deployment of the VM.
- Log in and check the operational ability of the VM.
| | PASS | PASS | PASS |
SP011 | Delete Snapshot and Deploy a Linux VM from the Template created from the Snapshot | - Delete the Snapshot of a ROOT Volume of a Linux VM.
- Deploy a VM using the Linux Template created from the Snapshot of a ROOT Volume of a Linux VM.
- Log in and check the operational ability of the VM.
| - Before Snapshot Deletion, Verify the snapshot's entry in the "snapshots" table. Verify that it is not marked as removed.
- Verify the presence of the corresponding snapshot on the Secondary Storage
- After Snapshot Deletion, Verify the snapshot's entry is marked as removed in the "snapshots" table.
- Verify the absence of the corresponding snapshot on the Secondary Storage
- Verify the Successful deployment of the VM.
- Log in and check the operational ability of the VM.
| | PASS | PASS | PASS |
SP012 | Delete Snapshot and Deploy a Windows VM from the Template created from the Snapshot | - Delete the Snapshot of a ROOT Volume of a Windows VM.
- Deploy a VM using the Windows Template created from the Snapshot of a ROOT Volume of a Windows VM.
- Log in and check the operational ability of the VM.
| - Before Snapshot Deletion, Verify the snapshot's entry in the "snapshots" table. Verify that it is not marked as removed.
- Verify the presence of the corresponding snapshot on the Secondary Storage
- After Snapshot Deletion, Verify the snapshot's entry is marked as removed in the "snapshots" table.
- Verify the absence of the corresponding snapshot on the Secondary Storage
- Verify the Successful deployment of the VM.
- Log in and check the operational ability of the VM.
| | PASS | PASS | PASS |
SP013 | Create Volume from a Snapshot of a ROOT disk of a Linux VM. | - Create a Snapshot of a ROOT Disk of a Linux VM.
- Create a Volume from the Snapshot.
| - Verify the snapshot's entry in the "snapshots" table.
- Verify the presence of the corresponding snapshot on the Secondary Storage.
- Verify the Volume's entry in the "Volume" table.
- Verify the presence of the corresponding volume on the Secondary Storage.
| | PASS | PASS | PASS |
SP014 | Create Volume from a Snapshot of a ROOT disk of a Windows VM. | - Create a Snapshot of a ROOT Disk of a Windows VM.
- Create a Volume from the Snapshot
| - Verify the snapshot's entry in the "snapshots" table.
- Verify the presence of the corresponding snapshot on the Secondary Storage.
- Verify the Volume's entry in the "Volume" table.
- Verify the presence of the corresponding volume on the Secondary Storage.
| | PASS | PASS | PASS |
SP015 | Attach the Volume created from the Snapshot of a ROOT disk of a Linux VM to the Same Linux VM | - Create a Snapshot of a ROOT Disk of a Linux VM.
- Create a Volume from the Snapshot.
- Attach the Volume to the Same Linux VM
| - Verify the snapshot's entry in the "snapshots" table.
- Verify the presence of the corresponding snapshot on the Secondary Storage.
- Verify the Volume's entry in the "Volume" table.
- Verify the presence of the corresponding volume on the Secondary Storage.
- Log into the VM and observe the existence of the new Volume under /dev
| | PASS | PASS | PASS |
SP016 | Attach the Volume created from the Snapshot of a ROOT disk of a Windows VM to the Same Windows VM | - Create a Snapshot of a ROOT Disk of a Windows VM.
- Create a Volume from the Snapshot.
- Attach the Volume to the Same Windows VM
| - Verify the snapshot's entry in the "snapshots" table.
- Verify the presence of the corresponding snapshot on the Secondary Storage.
- Verify the Volume's entry in the "Volume" table.
- Verify the presence of the corresponding volume on the Secondary Storage.
- Steps need to be provided.
| | PASS | PASS | PASS |
SP017 | Attach the Volume created from the Snapshot of a ROOT disk of a Linux VM to a different Linux VM | - Create a Snapshot of a ROOT Disk of a Linux VM.
- Create a Volume from the Snapshot.
- Deploy a Linux VM from a different Linux Template.
- Attach the Volume to the newly created Linux VM.
| - Verify the snapshot's entry in the "snapshots" table.
- Verify the presence of the corresponding snapshot on the Secondary Storage.
- Verify the Volume's entry in the "Volume" table.
- Verify the presence of the corresponding volume on the Secondary Storage.
- Log into the VM and observe the existence of the new Volume under /dev
| | PASS | PASS | PASS |
SP018 | Attach the Volume created from the Snapshot of a ROOT disk of a Windows VM to a Different Windows VM. | - Create a Snapshot of a ROOT Disk of a Windows VM.
- Create a Volume from the Snapshot.
- Deploy a Windows VM from a different Windows Template.
- Attach the Volume to the newly created Linux VM.
| - Verify the snapshot's entry in the "snapshots" table.
- Verify the presence of the corresponding snapshot on the Secondary Storage.
- Verify the Volume's entry in the "Volume" table.
- Verify the presence of the corresponding volume on the Secondary Storage.
- Steps need to be provided.
| | PASS | PASS | PASS |
SP019 | Detach the Attached Volume. The Attached Volume was created from the Snapshot of a ROOT disk of a Linux VM which was later attached to the same linux VM. | - Create a Snapshot of a ROOT Disk of a Linux VM.
- Create a Volume from the Snapshot.
- Attach the Volume to the Same Linux VM.
- Detach the Attached Volume.
| - Verify the snapshot's entry in the "snapshots" table.
- Verify the presence of the corresponding snapshot on the Secondary Storage.
- Verify the Volume's entry in the "Volume" table.
- Verify the presence of the corresponding volume on the Secondary Storage.
- Log into the VM and observe the existence of the new Volume under /dev
- After detaching the Volume, Log into the VM and observe the non-existence of the new Volume under /dev
| | PASS | PASS | PASS |
SP020 | Detach the Attached Volume. The Attached Volume was created from the Snapshot of a ROOT disk of a Windows VM which was later attached to the same Windows VM. | - Create a Snapshot of a ROOT Disk of a Windows VM.
- Create a Volume from the Snapshot.
- Attach the Volume to the Same Windows VM
- Detach the Attached Volume.
| - Verify the snapshot's entry in the "snapshots" table.
- Verify the presence of the corresponding snapshot on the Secondary Storage.
- Verify the Volume's entry in the "Volume" table.
- Verify the presence of the corresponding volume on the Secondary Storage.
- Steps need to be provided.
| | PASS | PASS | PASS |
SP021 | Detach the Attached Volume. The Attached Volume was created from the Snapshot of a ROOT disk of a Linux VM which was later attached to a different linux VM. | - Create a Snapshot of a ROOT Disk of a Linux VM.
- Create a Volume from the Snapshot.
- Deploy a Linux VM from a different Linux Template.
- Attach the Volume to the newly created Linux VM.
- Detach the Attached Volume.
| - Verify the snapshot's entry in the "snapshots" table.
- Verify the presence of the corresponding snapshot on the Secondary Storage.
- Verify the Volume's entry in the "Volume" table.
- Verify the presence of the corresponding volume on the Secondary Storage.
- Log into the VM and observe the existence of the new Volume under /dev
- After detaching the Volume, Log into the VM and observe the non-existence of the new Volume under /dev
| | PASS | PASS | PASS |
SP022 | Detach the Attached Volume. The Attached Volume was created from the Snapshot of a ROOT disk of a Windows VM which was later attached to a different Windows VM. | - Create a Snapshot of a ROOT Disk of a Windows VM.
- Create a Volume from the Snapshot.
- Deploy a Windows VM from a different Windows Template.
- Attach the Volume to the newly created Linux VM.
- Detach the Attached Volume.
| - Verify the snapshot's entry in the "snapshots" table.
- Verify the presence of the corresponding snapshot on the Secondary Storage.
- Verify the Volume's entry in the "Volume" table.
- Verify the presence of the corresponding volume on the Secondary Storage.
- Steps need to be provided.
| | PASS | PASS | PASS |
SP023 NA | Create a Chain of Snapshots of a ROOT disk of a Linux VM that resides on a Xenserver | - Set the Snapshot.delta.max as 3
- Restart the Management Server
- Deploy a VM from the default Linux Template along with a data disk.
- Log into the VM and create a file on the ROOT disk with content in it.
- Create a Snapshot of the ROOT disk.
- Repeat Steps 4 and 5 at least six times
- Step 6 will generate at least two 'chains' of Snapshots on the Secondary Storage.
| - Log in to the SSVM,
- Go to the directory where the secondary storage is mounted to.
- Go to the Snapshots directory on the secondary storage.
- Go to the account_id directory under Snapshots folder.
- Execute "vhd-util scan -p *.vhd".
- Output displays the chains of snapshots.
- Verify the Output
| | NA | NA | NA |
SP024 NA | Create a Chain of Snapshots of a Data disk of a Linux VM that resides on a Xenserver | - Set the Snapshot.delta.max as 3
- Restart the Management Server
- Deploy a VM from the default Linux Template along with a data disk.
- Log into the VM and create a ext3 file system on the Data Disk.
- Mount the Data Disk.
- Create a File with content on the Data Disk
- Create a Snapshot of the Data disk.
- Repeat Steps 6 and 7 at least six times
- Step 8 will generate at least two 'chains' of Snapshots on the Secondary Storage.
| - Log in to the SSVM,
- Go to the directory where the secondary storage is mounted to.
- Go to the Snapshots directory on the secondary storage.
- Go to the account_id directory under Snapshots folder.
- Execute "vhd-util scan -p *.vhd".
- Output displays the chains of snapshots.
- Verify the Output
| | NA | NA | NA |
SP025 NA | Create a Chain of Snapshots of a ROOT disk of a Linux VM that resides on a ESXi 4.0 Host | | | | NA | NA | NA |
SP026 NA | Create a Chain of Snapshots of a Data disk of a Linux VM that resides on a ESXi 4.0 Host | | | | NA | NA | NA |
SP027 NA | Create a Chain of Snapshots of a ROOT disk of a Linux VM that resides on a KVM Host | - Set the Snapshot.delta.max as 3
- Restart the Management Server
- Deploy a VM from the default Linux Template along with a data disk.
- Log into the VM and create a file on the ROOT disk with content in it.
- Create a Snapshot of the ROOT disk.
- Repeat Steps 4 and 5 at least six times
- Step 6 will generate at least two 'chains' of Snapshots on the Secondary Storage.
| - Log in to the SSVM,
- Go to the directory where the secondary storage is mounted to.
- Go to the Snapshots directory on the secondary storage.
- Go to the account_id directory under Snapshots folder.
- xenserver only: Execute "vhd-util scan -p *.vhd".
- Output displays the chains of snapshots.
- Verify the Outpu
| | NA | NA | NA |
SP028 NA | Create a Chain of Snapshots of a Data disk of a Linux VM that resides on a KVM Host | - Set the Snapshot.delta.max as 3
- Restart the Management Server
- Deploy a VM from the default Linux Template along with a data disk.
- Log into the VM and create a ext3 file system on the Data Disk.
- Mount the Data Disk.
- Create a File with content on the Data Disk
- Create a Snapshot of the Data disk.
- Repeat Steps 6 and 7 at least six times
- Step 8 will generate at least two 'chains' of Snapshots on the Secondary Storage.
| - Log in to the SSVM,
- Go to the directory where the secondary storage is mounted to.
- Go to the Snapshots directory on the secondary storage.
- Go to the account_id directory under Snapshots folder.
- xenserver only: Execute "vhd-util scan -p *.vhd".
- Output displays the chains of snapshots.
- Verify the Output
| | NA | NA | NA |
SP029 NA | Delete a Full Snapshot present in the Chain of Snapshots | - Set the Snapshot.delta.max as 3
- Restart the Management Server
- Deploy a VM from the default Linux Template along with a data disk.
- Log into the VM and create a file on the ROOT disk with content in it.
- Create a Snapshot of the ROOT disk.
- Repeat Steps 4 and 5 at least six times
- Step 6 will generate at least two 'chains' of Snapshots on the Secondary Storage.
- The 1st ,4th ,7th ,10th ,....n+3 Snapshots are Full Snapshots of 'n' Snapshot chains
- Delete (i)th Full Snapshot and Verify the Usability of (i+1)th and (i+2)th Snapshots
- Verify the Usability of the Snapshots by performing any of the above mentioned tests on the Snapshots
| - Log in to the SSVM,
- Go to the directory where the secondary storage is mounted to.
- Go to the Snapshots directory on the secondary storage.
- Go to the account_id directory under Snapshots folder.
- xenserver only: Execute "vhd-util scan -p *.vhd".
- Output displays the chains of snapshots.
- Verify the Output.
- Execute Step 5 after Snapshot Deletion and check the existence of the deleted Snapshot in the chain. The Snapshot is not deleted on the secondary storage as there are other snapshots in the chain that depend on the Deleted Snapshot.
- Observe that the Snapshot is marked removed on the "snapshots" table.
| | NA | NA | NA |
SP030 NA | Delete a Delta Snapshot present in the Chain of Snapshots | - Set the Snapshot.delta.max as 3
- Restart the Management Server
- Deploy a VM from the default Linux Template along with a data disk.
- Log into the VM and create a file on the ROOT disk with content in it.
- Create a Snapshot of the ROOT disk.
- Repeat Steps 4 and 5 at least six times
- Step 6 will generate at least two 'chains' of Snapshots on the Secondary Storage.
- The 1st ,4th ,7th ,10th ,....n+3 Snapshots are Full Snapshots of 'n' Snapshot chains.
- Remaining Snapshots other than the above mentioned Snapshots are Delta Snapshots.
- Delete (i+1)th Delta Snapshot where (i)th Snapshot is a Full Snapshot and (i+2)th Snapshot is a Delta Snapshot. Verify the Usability of (i)th and (i+2)th Snapshots after the deletion of the (i)th Snapshot.
- Verify the Usability of the Snapshots by performing any of the above mentioned tests on the Snapshots
| - Log in to the SSVM,
- Go to the directory where the secondary storage is mounted to.
- Go to the Snapshots directory on the secondary storage.
- Go to the account_id directory under Snapshots folder.
- xenserver only: Execute "vhd-util scan -p *.vhd".
- Output displays the chains of snapshots.
- Verify the Output.
- Execute Step 5 after Snapshot Deletion and check the existence of the deleted Snapshot in the chain. The Snapshot is not deleted on the secondary storage as there are other snapshots in the chain that depend on the Deleted Snapshot.
- Observe that the Snapshot is marked removed on the "snapshots" table.
| | NA | NA | NA |
SP031 NA | Delete all the Snapshots present in the Chain of Snapshots | - Set the Snapshot.delta.max as 3
- Restart the Management Server
- Deploy a VM from the default Linux Template along with a data disk.
- Log into the VM and create a file on the ROOT disk with content in it.
- Create a Snapshot of the ROOT disk.
- Repeat Steps 4 and 5 at least six times
- Step 6 will generate at least two 'chains' of Snapshots on the Secondary Storage.
- Delete 1st, 2nd and 3rd Snapshots.
- Observe the entire chain of snapshots missing on the Secondary Storage.
| - Log in to the SSVM,
- Go to the directory where the secondary storage is mounted to.
- Go to the Snapshots directory on the secondary storage.
- Go to the account_id directory under Snapshots folder.
- xenserver only: Execute "vhd-util scan -p *.vhd".
- Output displays the chains of snapshots.
- Verify the Output.
- Execute Step 5 after deleting all the snapshots present in a chain. The chain should no longer exist on the secondary storage. All snapshots belonging to the chain should be missing on the secondary storage.
| | NA | NA | NA |
SP032 | Try to create a Snapshot of a ROOT Volume of a Destroyed VM (Not expunged yet) | - This test need not be done if the Customer is not using Cloud Stack UI
- Deploy a VM from the Default Linux Template.
- Set the "expunge.interval" and "expunge.delay" to 900 seconds(15 mins)
- Restart the CloudStack Management Server.
- Destroy the VM.
- Using "createSnapshot" API, try to create a Snaphot of the ROOT Volume of the destroyed VM (not expunged yet).
| - Snapshot Creation should Fail.
| | PASS | PASS | PASS |
SP033 | When account is removed, all snapshots belonging to this account should be removed from Secondary Storage | - Create an account.
- Log in as the user of the account.
- Deploy a VM using the default Linux template.
- Create a Snapshot of the ROOT Volume of the VM.
- Repeat Steps 3 and 4, three times.
- Step 5 generates three Snapshots.
- Delete the Account.
- Observe that the snapshots are removed from the secondary storage.
| - Before Snapshots Deletion, Verify the snapshots' entries in the "snapshots" table. Verify that they are not marked as removed.
- Verify the presence of the corresponding snapshots on the Secondary Storage
- After Deleting the Account, Verify the snapshots' entries of the corresponding Account are marked as removed in the "snapshots" table.
- Verify the absence of the corresponding snapshots on the Secondary Storage
| | PASS | PASS | PASS |
SP034 | Create Snapshot of an Attached Volume | - Deploy a VM using the Default CentOS Template.
- Create a Volume.
- Attach the Volume to the VM deployed in Step 1.
- Log into the VM and create a ext3 file system on the Data Disk.
- Mount the Data Disk.
- Create a File with content on the Data Disk
- Create a Snapshot of the Data disk.
| - Verify the snapshot's entry in the "snapshots" table.
- Verify the presence of the corresponding snapshot on the Secondary Storage
| | PASS | PASS | PASS |
SP035 | Create Snapshot of a Detached Volume | - Deploy a VM using the Default CentOS Template.
- Create a Volume.
- Attach the Volume to the VM deployed in Step 1.
- Log into the VM and create a ext3 file system on the Data Disk.
- Mount the Data Disk.
- Create a File with content on the Data Disk
- Unmount the Data Disk from the VM.
- Create a Snapshot of the Data disk.
| - Verify the snapshot's entry in the "snapshots" table.
- Verify the presence of the corresponding snapshot on the Secondary Storage
| | PASS | PASS | PASS |
SP036 | Delete Snapshot of an Attached Volume | - Deploy a VM using the Default CentOS Template.
- Create a Volume.
- Attach the Volume to the VM deployed in Step 1.
- Log into the VM and create a ext3 file system on the Data Disk.
- Mount the Data Disk.
- Create a File with content on the Data Disk
- Create a Snapshot of the Data disk.
- Delete the Snapshot.
- Log into the VM and check the usability of the VM.
| - Before Snapshot Deletion, Verify the snapshot's entry in the "snapshots" table. Verify that it is not marked as removed.
- Verify the presence of the corresponding snapshot on the Secondary Storage
- After Snapshot Deletion, Verify the snapshot's entry is marked as removed in the "snapshots" table.
- Verify the absence of the corresponding snapshot on the Secondary Storage
- Verify the Successful deployment of the VM.
- Log in and check the operational ability of the VM.
| | PASS | PASS | PASS |
SP037 | Delete Snapshot of a Detached Volume | - Deploy a VM using the Default CentOS Template.
- Create a Volume.
- Attach the Volume to the VM deployed in Step 1.
- Log into the VM and create a ext3 file system on the Data Disk.
- Mount the Data Disk.
- Create a File with content on the Data Disk
- Unmount the Data Disk from the VM.
- Create a Snapshot of the Data disk.
- Delete the Snapshot.
- Log into the VM and check the usability of the VM.
| - Before Snapshot Deletion, Verify the snapshot's entry in the "snapshots" table. Verify that it is not marked as removed.
- Verify the presence of the corresponding snapshot on the Secondary Storage
- After Snapshot Deletion, Verify the snapshot's entry is marked as removed in the "snapshots" table.
- Verify the absence of the corresponding snapshot on the Secondary Storage
- Verify the Successful deployment of the VM.
- Log in and check the operational ability of the VM.
| | PASS | PASS | PASS |
SP038 | Create Hourly recurring snapshots for ROOT disk and data disks (limits, snapshot retention and auto deletion) | - Deploy a VM using the Default CentOS Template
- Create an Hourly Recurring snapshot policy on the ROOT disk.
- Observe the creation of a Snapshot after an hour.
| - Verify the snapshot's entry in the "snapshots" table.
- Verify that the Snapshot's snapshot_type is HOURLY in the "snapshots" table.
- Verify the presence of the corresponding snapshot on the Secondary Storage
| | PASS | PASS | PASS |
SP039 | Create Daily recurring snapshots for ROOT disk and data disks (limits, snapshot retention and auto deletion) | - Deploy a VM using the Default CentOS Template
- Create an Daily Recurring snapshot policy on the ROOT disk.
- Change the time on the host on which the management server is running***. Change the time to Current time + 23 hours.
- Restart the Management Server.
- Observe the creation of a Snapshot after an hour.
- ***Caution: Changing the Server time for the purpose of testing recurring snapshots might affect other time dependent features of CloudStack
| - Verify the snapshot's entry in the "snapshots" table.
- Verify that the Snapshot's snapshot_type is DAILY in the "snapshots" table.
- Verify the presence of the corresponding snapshot on the Secondary Storage
| | PASS | PASS | PASS |
SP040 | Create Weekly recurring snapshots for ROOT disk and data disks (limits, snapshot retention and auto deletion) | - Deploy a VM using the Default CentOS Template
- Create an Daily Recurring snapshot policy on the ROOT disk.
- Change the time on the host on which the management server is running***. Change the time to Current time + 6 Days + 23 hours.
- Restart the Management Server.
- Observe the creation of a Snapshot after an hour.
- ***Caution: Changing the Server time for the purpose of testing recurring snapshots might affect other time dependent features of CloudStack
| - Verify the snapshot's entry in the "snapshots" table.
- Verify that the Snapshot's snapshot_type is WEEKLY in the "snapshots" table.
- Verify the presence of the corresponding snapshot on the Secondary Storage
| | PASS | PASS | PASS |
SP041 | Create Monthly recurring snapshots for ROOT disk and data disks (limits, snapshot retention and auto deletion) | - Deploy a VM using the Default CentOS Template
- Create an Daily Recurring snapshot policy on the ROOT disk.
- Change the time on the host on which the management server is running***. Change the time to Current time + (27/28/29/30- depending on the Month (Feb/Leap yr Feb/30 days moth/31 days month)) Days + 23 hours.
- Restart the Management Server.
- Observe the creation of a Snapshot after an hour.
- ***Caution: Changing the Server time for the purpose of testing recurring snapshots might affect other time dependent features of CloudStack
| - Verify the snapshot's entry in the "snapshots" table.
- Verify that the Snapshot's snapshot_type is MONTHLY in the "snapshots" table.
- Verify the presence of the corresponding snapshot on the Secondary Storage
| | PASS | PASS | PASS |
SP042 | while performing snapshot migrate ROOT volume to other primary storage | - Deploy a VM with data disk using the Default CentOS Template
- Create additional primary storage
- while snapshot of ROOT volume ongoing, Volume migrate ROOT volume to other primary storage
| 3. VM in running state. snapshot of ROOT volume successful. volume migration of ROOT volume successful | | PASS | PASS | PASS |
SP043 | while performing snapshot migrate DATA volume to other primary storage | - Deploy a VM with data disk using the Default CentOS Template
- Create additional primary storage
- while snapshot of DATA volume ongoing, Volume migrate DATA volume to other primary storage
| 3. VM in running state. snapshot of DATA volume successful. volume migration of DATA volume successful | | PASS | PASS | PASS |
SP044 | create volume attach volume to VM | - create volume
- attach volume to VM
| attach volume should succeed | | https://issues.citrite.net/browse/CS-20731 FAIL PASS | https://issues.citrite.net/browse/CS-20731 FAIL PASS | PASS |
| kvm qemu change specific test cases | Steps To Be Performed to Test | Verification Steps | | rhel 6.3 | | |
SP045 | VM sync- when snapshot in progress, kvm host "virsh list" shows VM in "Paused" state | - Deploy a Linux VM using CentOS
- Perform snapshot on root disk ofVM
- While snapshot in progress, on KVM host issue "virsh list" command
| 3. on kvm host "virsh list" should show VM in "Paused" state MS UI should show VM in "Running" state | | [root@guepardo agent]# virsh list Id Name State 1 v-1-VM running 2 s-2-VM running 3 r-5-VM running 4 i-2-4-VM paused 7 i-2-8-VM paused 8 i-2-10-VM paused PASS | | |
SP046 | As VM memory size increases, VM pause time increases during snapshot | - Deploy Linux VMs using CentOS , memory size 512 MB to 16 GB same ROOT DATA disk size 20GB to 400 GB
- Perform snapshot on root & data disk of VM
- While snapshot in progress, on KVM host use "virsh list" to monitor VM pausetime
- record memory, pause time, log statement
| 4. As VM memory size increase VM pause time increase during snapshot. depend on size of guest memory from few seconds to 30~40 seconds | | Volume vol size mem pause ROOT-4 8GB 12GB 42 sec ROOT-10 8GB 1GB 33 sec ROOT-8 8GB 512MB 30 sec DATA-4 400GB 12GB 33 sec DATA-10 615 GB 1GB 26 sec PASS | | |
SP046 | | | | | "ROOT-4","size":8589934592 snapshot takes 20 seconds "ROOT-8","size":8589934592 snapshot takes 40 seconds "ROOT-10","size":8589934592 snapshot takes 27 seconds "DATA-4","size":429496729600 snapshot takes 26 seconds "DATA-10" size 660351221760 snapshot takes 9 seconds "DATA-8","size":659277479936 snapshot takes 9 seconds * | | |
| | | | | | | |
SP047 | Parallel snapshot for different VMs with large memory size on same host | - Deploy 5 Linux VMs memory 512 MB to 16 GB ROOT DATA disk size 20GB to 400 GB
- Perform parallel snapshot recurrrent scheduled root & data disk of VM
- While snapshot in progress, on KVM host use "virsh list" to monitor VM pausetime
- record memory, pause time, log statement
| 2. parallel snapshot should all succeed 4. As VM memory size increase VM pause time increase during snapshot. depend on size of guest memory from few seconds to 30~40 seconds | | PASS | | |
SP048 | In RHEL 6.5 when snapshot in progress kill snapshot process | - Deploy 5 Linux VMs using CentOS , memory size 512 MB to 16 GB same ROOT DATA disk size 20GB to 400 GB
- Perform snapshot on root & data disk of these VM of memory size.
- While snapshot in progress on KVM host, ps -ef | grep ccp-qemu.img
- kill -9 <ccp-qemu.img process>
| 3. find ccp-qemu.img process id 4. kill -9 <ccp-qemu.img process> snapshot should fail snapshot should be shown in "error" state | | PASS | | |
SP049 | mysql host_details show qemu version # agent version # https://issues.citrite.net/browse/CS-21294 | mysql host_details table show qemu version # agent version # | mysql host_details table show qemu version # agent version # | | name:Host.OS.Kernel.Version value: 2.6.32-279.el6.x86_64 name:CCP.KVM.Agent.Version value: cloudstack-agent-4.5.0-SNAPSHOT.el6.x86_64 PASS | | |
| existence/addition/removal kvm custom qemu package in fresh install & upgrade | | | | | | |
SP050 | existence/removal kvm custom qemu packages in fresh install : base OS rhel 6.3 CCP prior Goleta release https://issues.citrite.net/browse/CP-9477 | - fresh install base OS rhel 6.3 CCP prior Goleta release.
- rpm -qa | grep kvm
record qemu-kvm & qemu-img rpm version
| 2. qemu-img & qemu-kvm package versions show custom: qemu-kvm-0.12.1.2-3.295.el6.10.x86_64 qemu-img-0.12.1.2-3.295.el6.10.x86_64 | | qemu-kvm-0.12.1.2-3.295.el6.10.x86_64 qemu-img-0.12.1.2-3.295.el6.10.x86_64 PASS | | |
SP051 | existence/removal kvm custom qemu package in fresh install: base OS rhel 6.3 CCP Goleta 4.5 release | - fresh install base OS rhel 6.3 CCP Goleta release.
- rpm -qa | grep kvm
record qemu-kvm & qemu-img rpm version
| 2. qemu-img & qemu-kvm package versions show default: qemu-kvm-0.12.1.2-2.295.el6.x86_64 qemu-img-0.12.1.2-2.295.el6.x86_64 | | qemu-kvm-0.12.1.2-2.295.el6.x86_64 qemu-img-0.12.1.2-2.295.el6.x86_64 PASS | | |
SP052 | existence/removal kvm custom qemu package in fresh install : base OS rhel 6.4 CCP Goleta 4.5 release | - fresh install base OS rhel 6.4 CCP Goleta release.
- rpm -qa | grep kvm
record qemu-kvm & qemu-img rpm version
| 2. qemu-img & qemu-kvm package versions show default: qemu-kvm-0.12.1.2-2.355.el6.x86_64 qemu-img-0.12.1.2-2.355.el6.x86_64 | | qemu-kvm-0.12.1.2-2.355.el6.x86_64 qemu-img-0.12.1.2-2.355.el6.x86_64 PASS | | |
SP053 | existence/removal kvm custom qemu package in fresh install : base OS rhel 6.5 CCP Goleta 4.5 release | - fresh install base OS rhel 6.5 CCP Goleta release.
- rpm -qa | grep kvm
record qemu-kvm & qemu-img rpm version
| 2. qemu-img & qemu-kvm package versions show default: qemu-kvm-0.12.1.2-2.415.el6.x86_64 qemu-img-0.12.1.2-2.415.el6.x86_64 ccp-qemu-img-1.0-1.x86_64 | | qemu-kvm-0.12.1.2-2.415.el6.x86_64 qemu-img-0.12.1.2-2.415.el6.x86_64 ccp-qemu-img-1.0-1.x86_64 PASS | | |
SP054 | existence/removal kvm custom qemu package in upgrade to: base OS rhel 6.3 CCP prior Goleta upgrade base OS rhel 6.3 CCP Goleta 4.5 | - fresh install base OS rhel 6.3 CCP prior Goleta
- upgrade base OS rhel 6.3 CCP Goleta 4.5
| 2. qemu-kvm-0.12.1.2-2.295.el6.x86_64 qemu-img-0.12.1.2-2.295.el6.x86_64 | | | | |
SP055 | existence/removal kvm custom qemu package in upgrade to: base OS rhel 6.3 CCP Goleta upgrade base OS rhel 6.5 CCP Goleta 4.5 |
- fresh install base OS rhel 6.3 CCP Goleta
- upgrade base OS rhel 6.5 CCP Goleta 4.5
| 2. qemu-kvm-0.12.1.2-2.415.el6.x86_64 qemu-img-0.12.1.2-2.415.el6.x86_64 ccp-qemu-img-1.0-1.x86_64 | | | | |
| | | | | | | |
| | | | | | | |
| kvm qemu change automation | | | | | | |
SP061 | automation: smoke/test_snapshots.py | | | | PASS | PASS | PASS |
SP062 | automation: component/test_recurring_snapshots.py | | | | some fail | some fail | some fail |
SP063 | automation: component/test_snapshot_gc.py | | | | some fail | some fail | some fail |
SP064 | automation: component/test_snapshot_limits.py | | | | PASS | PASS | PASS |
SP065 | automation: component/test_snapshots.py | | | | some fail | some fail | some fail |
SP066 | automation: component/test_snapshots_improvement.py | | | | some fail | some fail | some fail |
SP067 | automation: component/test_escalations_snapshots.py | | | | some fail | some fail | some fail |
| kvm qemu change upgrade with base OS upgrade | | | | | | |
SP072 | Upgrade with base OS upgrade rhel6.3 CPP 3.0.7 patchF -> rhel6.5 CPP 4.5 | | | | https://issues.citrite.net/browse/CS-20890 https://issues.citrite.net/browse/CS-21323 | | |
SP073 | Upgrade with base OS upgrade rhel6.3 CPP 4.2.1 -> rhel6.5 CPP 4.5 | | | | https://issues.citrite.net/browse/CS-20890 https://issues.citrite.net/browse/CS-21323 | | |
SP074 | Upgrade with base OS upgrade rhel6.3 CPP 4.3.0.1 -> rhel6.5 CPP 4.5 | | | | https://issues.citrite.net/browse/CS-20890 https://issues.citrite.net/browse/CS-21324 | | |
| kvm qemu change upgrade without base OS upgrade | | | | | | |
SP075 | Upgrade rhel6.3 CPP 3.0.7 patchF -> rhel6.3 CPP 4.5 | | | | https://issues.citrite.net/browse/CS-20982 | | |
SP076 | Upgrade rhel6.3 CPP 4.2.1 -> rhel6.3 CPP 4.5 | | | | https://issues.citrite.net/browse/CS-20974 | | |
SP077 | Upgrade rhel6.3 CPP 4.3.0.1 -> rhel6.3 CPP 4.5 | | | | https://issues.citrite.net/browse/CS-20986 https://issues.citrite.net/browse/CS-21033 | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |