Test ID

Test Case Name                           

Steps To Be Performed to Test

Verification Steps

RHEL6.2        

RHEL 6.3 

 

RHEL6.4     RHEL6.5   
        
SP001Take snapshot on root disk of a Linux VM
  1. Deploy a Linux VM using default CentOS template, use small service offering, disk offering
  2. Log into the VM and create a file with content in it.
  3. Perform snapshot on the root disk of this newly created VM
  1. Verify the snapshot's entry in the "snapshots" table.
  2. 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.

  1. Register/Create a Windows Template onto the CloudStack Setup.
  2. Deploy a Windows VM using the Windows template, use medium service offering, disk offering
  3. Log into the VM and create a file on the desktop with content in it.
  4. Perform snapshot on the root disk of this newly created VM
  1. Verify the snapshot's entry in the "snapshots" table.
  2. 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.

  1. Deploy a Linux VM using default CentOS template, use small service offering, disk offering.
  2. Log into the VM and create a ext3 file system on the Data Disk.
  3. Mount the Data Disk.
  4. Create a File with content
    on the Data Disk
  5. Perform snapshot on the data disk of this newly created VM
  1. Verify the snapshot's entry in the "snapshots" table.
  2. 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.

  1. Verify the snapshot's entry in the "snapshots" table.
  2. 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

  1. Create a Snapshot.
  2. Observe the events table for the corresponding "SNAPSHOT.CREATE" event.
  3. Steps need to be provided.
  1. Observe the events table for the corresponding "SNAPSHOT.CREATE" event.
 

PASS

 

PASSPASS

SP006

Event Generation during Snapshot Deletion

  1. Delete a Snapshot.
  2. Observe the events table for the corresponding  "SNAPSHOT.DELETE" event.
  3. Steps need to be provided.
  1. Observe the events table for the corresponding "SNAPSHOT.DELETE" event.
 

PASS

PASSPASS

SP007

Create Template from a Snapshot of a ROOT disk of a Linux VM.

  1. Create a Snapshot of a ROOT Volume of a Linux VM.
  2. Create a Template from the Snapshot with the appropriate Guest_os_type selected.
  1. Verify the template's entry in the "template_host_ref" table.
  2. Verify the presence of the corresponding template on the Secondary Storage
 

PASS

PASSPASS

SP008

Create Template from a Snapshot of a ROOT disk of a Windows VM.

  1. Create a Snapshot of a ROOT Volume of a Linux VM.
  2. Create a Template from the Snapshot with the appropriate Guest_os_type selected
  1. Verify the template's entry in the "template_host_ref" table.
  2. Verify the presence of the corresponding template on the Secondary Storage
 

PASS

PASSPASS

SP009

Deploy a Linux VM from the Template created from the Snapshot

  1. Deploy a VM using the Linux Template created from the Snapshot of a ROOT Volume of a Linux VM.
  2. Log in and check the operational ability of the VM.
  1. Verify the Successful deployment of the VM.
  2. Log in and check the operational ability of the VM.
 

PASS

PASSPASS

SP010

Deploy a Windows VM from the Template created from the Snapshot

  1. Deploy a VM using the Windows Template created from the Snapshot of a ROOT Volume of a Windows VM.
  2. Log in and check the operational ability of the VM.
  1. Verify the Successful deployment of the VM.
  2. Log in and check the operational ability of the VM.
 

PASS

PASSPASS

SP011

Delete Snapshot and Deploy a Linux VM from the Template created from the Snapshot

  1. Delete the Snapshot of a ROOT Volume of a Linux VM.
  2. Deploy a VM using the Linux Template created from the Snapshot of a ROOT Volume of a Linux VM.
  3. Log in and check the operational ability of the VM.
  1. Before Snapshot Deletion, Verify the snapshot's entry in the "snapshots" table. Verify that it is not marked as removed.
  2. Verify the presence of the corresponding snapshot on the Secondary Storage
  3. After Snapshot Deletion, Verify the snapshot's entry is marked as removed in the "snapshots" table.
  4. Verify the absence of the corresponding snapshot on the Secondary Storage
  5. Verify the Successful deployment of the VM.
  6. Log in and check the operational ability of the VM.
 

PASS

PASSPASS

SP012

Delete Snapshot and Deploy a Windows VM from the Template created from the Snapshot

  1. Delete the Snapshot of a ROOT Volume of a Windows VM.
  2. Deploy a VM using the Windows Template created from the Snapshot of a ROOT Volume of a Windows VM.
  3. Log in and check the operational ability of the VM.
  1. Before Snapshot Deletion, Verify the snapshot's entry in the "snapshots" table. Verify that it is not marked as removed.
  2. Verify the presence of the corresponding snapshot on the Secondary Storage
  3. After Snapshot Deletion, Verify the snapshot's entry is marked as removed in the "snapshots" table.
  4. Verify the absence of the corresponding snapshot on the Secondary Storage
  5. Verify the Successful deployment of the VM.
  6. Log in and check the operational ability of the VM.
 

PASS

PASSPASS

SP013

Create Volume from a Snapshot of a ROOT disk of a Linux VM.

  1. Create a Snapshot of a ROOT Disk of a Linux VM.
  2. Create a Volume from the Snapshot.
  1. Verify the snapshot's entry in the "snapshots" table.
  2. Verify the presence of the corresponding snapshot on the Secondary Storage.
  3. Verify the Volume's entry in the "Volume" table.
  4. Verify the presence of the corresponding volume on the Secondary Storage.
 

PASS

PASSPASS

SP014

Create Volume from a Snapshot of a ROOT disk of a Windows VM.

  1. Create a Snapshot of a ROOT Disk of a Windows VM.
  2. Create a Volume from the Snapshot
  1. Verify the snapshot's entry in the "snapshots" table.
  2. Verify the presence of the corresponding snapshot on the Secondary Storage.
  3. Verify the Volume's entry in the "Volume" table.
  4. Verify the presence of the corresponding volume on the Secondary Storage.
 

PASS

PASSPASS

SP015

Attach the Volume created from the Snapshot of a ROOT disk of a Linux VM to the Same Linux VM

  1. Create a Snapshot of a ROOT Disk of a Linux VM.
  2. Create a Volume from the Snapshot.
  3. Attach the Volume to the Same Linux VM
  1. Verify the snapshot's entry in the "snapshots" table.
  2. Verify the presence of the corresponding snapshot on the Secondary Storage.
  3. Verify the Volume's entry in the "Volume" table.
  4. Verify the presence of the corresponding volume on the Secondary Storage.
  5. Log into the VM and observe the existence of the new Volume under /dev
 

PASS

PASSPASS

SP016

Attach the Volume created from the

Snapshot of a ROOT disk of a Windows

VM to the Same Windows VM

  1. Create a Snapshot of a ROOT Disk of a Windows VM.
  2. Create a Volume from the Snapshot.
  3. Attach the Volume to the Same Windows VM
  1. Verify the snapshot's entry in the "snapshots" table.
  2. Verify the presence of the corresponding snapshot on the Secondary Storage.
  3. Verify the Volume's entry in the "Volume" table.
  4. Verify the presence of the corresponding volume on the Secondary Storage.
  5. Steps need to be provided.
 

PASS

PASSPASS

SP017

Attach the Volume created from the

Snapshot of a ROOT disk of a Linux

VM to a different Linux VM

  1. Create a Snapshot of a ROOT Disk of a Linux VM.
  2. Create a Volume from the Snapshot.
  3. Deploy a Linux VM from a different Linux Template.
  4. Attach the Volume to the newly created Linux VM.
  1. Verify the snapshot's entry in the "snapshots" table.
  2. Verify the presence of the corresponding snapshot on the Secondary Storage.
  3. Verify the Volume's entry in the "Volume" table.
  4. Verify the presence of the corresponding volume on the Secondary Storage.
  5. Log into the VM and observe the existence of the new Volume under /dev
 

PASS

PASSPASS

SP018

Attach the Volume created from the Snapshot of a ROOT disk of a Windows VM to a Different Windows VM.

  1. Create a Snapshot of a ROOT Disk of a Windows VM.
  2. Create a Volume from the Snapshot.
  3. Deploy a Windows VM from a different Windows Template.
  4. Attach the Volume to the newly created Linux VM.
  1. Verify the snapshot's entry in the "snapshots" table.
  2. Verify the presence of the corresponding snapshot on the Secondary Storage.
  3. Verify the Volume's entry in the "Volume" table.
  4. Verify the presence of the corresponding volume on the Secondary Storage.
  5. Steps need to be provided.
 

PASS

PASSPASS

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.

  1. Create a Snapshot of a ROOT Disk of a Linux VM.
  2. Create a Volume from the Snapshot.
  3. Attach the Volume to the Same Linux VM.
  4. Detach the Attached Volume.
  1. Verify the snapshot's entry in the "snapshots" table.
  2. Verify the presence of the corresponding snapshot on the Secondary Storage.
  3. Verify the Volume's entry in the "Volume" table.
  4. Verify the presence of the corresponding volume on the Secondary Storage.
  5. Log into the VM and observe the existence of the new Volume under /dev
  6. After detaching the Volume, Log into the VM and observe the non-existence of the new Volume under /dev
 

PASS

PASSPASS

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.

  1. Create a Snapshot of a ROOT Disk of a Windows VM.
  2. Create a Volume from the Snapshot.
  3. Attach the Volume to the Same Windows VM
  4. Detach the Attached Volume.
  1. Verify the snapshot's entry in the "snapshots" table.
  2. Verify the presence of the corresponding snapshot on the Secondary Storage.
  3. Verify the Volume's entry in the "Volume" table.
  4. Verify the presence of the corresponding volume on the Secondary Storage.
  5. Steps need to be provided.
 

PASS

PASSPASS

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.

  1. Create a Snapshot of a ROOT Disk of a Linux VM.
  2. Create a Volume from the Snapshot.
  3. Deploy a Linux VM from a different Linux Template.
  4. Attach the Volume to the newly created Linux VM.
  5. Detach the Attached Volume.
  1. Verify the snapshot's entry in the "snapshots" table.
  2. Verify the presence of the corresponding snapshot on the Secondary Storage.
  3. Verify the Volume's entry in the "Volume" table.
  4. Verify the presence of the corresponding volume on the Secondary Storage.
  5. Log into the VM and observe the existence of the new Volume under /dev
  6. After detaching the Volume, Log into the VM and observe the non-existence of the new Volume under /dev
 

PASS

PASSPASS

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.

  1. Create a Snapshot of a ROOT Disk of a Windows VM.
  2. Create a Volume from the Snapshot.
  3. Deploy a Windows VM from a different Windows Template.
  4. Attach the Volume to the newly created Linux VM.
  5. Detach the Attached Volume.
  1. Verify the snapshot's entry in the "snapshots" table.
  2. Verify the presence of the corresponding snapshot on the Secondary Storage.
  3. Verify the Volume's entry in the "Volume" table.
  4. Verify the presence of the corresponding volume on the Secondary Storage.
  5. Steps need to be provided.
 

PASS

PASSPASS

SP023

NA

Create a Chain of Snapshots of a ROOT disk of a Linux VM that resides on a Xenserver

  1. Set the Snapshot.delta.max as 3
  2. Restart the Management Server
  3. Deploy a VM from the default Linux Template along with a data disk.
  4. Log into the VM and create a file on the ROOT disk with content in it.
  5. Create a Snapshot of the ROOT disk.
  6. Repeat Steps 4 and 5 at least six times
  7. Step 6 will generate at least two 'chains' of Snapshots on the Secondary Storage.
  1. Log in to the SSVM,
  2. Go to the directory where the secondary storage is mounted to.
  3. Go to the Snapshots directory on the secondary storage.
  4. Go to the account_id directory under Snapshots folder.
  5. Execute "vhd-util scan -p *.vhd".
  6. Output displays the chains of snapshots.
  7. Verify the Output
 

NA

NANA

SP024

NA

Create a Chain of Snapshots of a Data disk of a Linux VM that resides on a Xenserver

  1. Set the Snapshot.delta.max as 3
  2. Restart the Management Server
  3. Deploy a VM from the default Linux Template along with a data disk.
  4. Log into the VM and create a ext3 file system on the Data Disk.
  5. Mount the Data Disk.
  6. Create a File with content on the Data Disk
  7. Create a Snapshot of the Data disk.
  8. Repeat Steps 6 and 7 at least six times
  9. Step 8 will generate at least two 'chains' of Snapshots on the Secondary Storage.
  1. Log in to the SSVM,
  2. Go to the directory where the secondary storage is mounted to.
  3. Go to the Snapshots directory on the secondary storage.
  4. Go to the account_id directory under Snapshots folder.
  5. Execute "vhd-util scan -p *.vhd".
  6. Output displays the chains of snapshots.
  7. Verify the Output
 

NA

NANA

SP025

NA

Create a Chain of Snapshots of a ROOT disk of a Linux VM that resides on a ESXi 4.0 Host

 

 

 

NA

NANA

SP026

NA

Create a Chain of Snapshots of a Data disk of a Linux VM that resides on a ESXi 4.0 Host

 

 

 

NA

NANA

SP027

NA

Create a Chain of Snapshots of a ROOT disk of a Linux VM that resides on a KVM Host

  1. Set the Snapshot.delta.max as 3
  2. Restart the Management Server
  3. Deploy a VM from the default Linux Template along with a data disk.
  4. Log into the VM and create a file on the ROOT disk with content in it.
  5. Create a Snapshot of the ROOT disk.
  6. Repeat Steps 4 and 5 at least six times
  7. Step 6 will generate at least two 'chains' of Snapshots on the Secondary Storage.
  1. Log in to the SSVM,
  2. Go to the directory where the secondary storage is mounted to.
  3. Go to the Snapshots directory on the secondary storage.
  4. Go to the account_id directory under Snapshots folder.
  5. xenserver  only: Execute "vhd-util scan -p *.vhd".
  6. Output displays the chains of snapshots.
  7. Verify the Outpu
 

NA

NANA

SP028

NA

Create a Chain of Snapshots of a Data disk of a Linux VM that resides on a KVM Host

  1. Set the Snapshot.delta.max as 3
  2. Restart the Management Server
  3. Deploy a VM from the default Linux Template along with a data disk.
  4. Log into the VM and create a ext3 file system on the Data Disk.
  5. Mount the Data Disk.
  6. Create a File with content on the Data Disk
  7. Create a Snapshot of the Data disk.
  8. Repeat Steps 6 and 7 at least six times
  9. Step 8 will generate at least two 'chains' of Snapshots on the Secondary Storage.
  1. Log in to the SSVM,
  2. Go to the directory where the secondary storage is mounted to.
  3. Go to the Snapshots directory on the secondary storage.
  4. Go to the account_id directory under Snapshots folder.
  5. xenserver only:  Execute "vhd-util scan -p *.vhd".
  6. Output displays the chains of snapshots.
  7. Verify the Output
 

NA

NANA

SP029

NA

Delete a Full Snapshot present in the Chain of Snapshots

  1. Set the Snapshot.delta.max as 3
  2. Restart the Management Server
  3. Deploy a VM from the default Linux Template along with a data disk.
  4. Log into the VM and create a file on the ROOT disk with content in it.
  5. Create a Snapshot of the ROOT disk.
  6. Repeat Steps 4 and 5 at least six times
  7. Step 6 will generate at least two 'chains' of Snapshots on the Secondary Storage.
  8. The 1st ,4th ,7th ,10th ,....n+3 Snapshots are Full Snapshots of 'n' Snapshot chains
  9. Delete (i)th Full Snapshot and Verify the Usability of (i+1)th and (i+2)th Snapshots
  10. Verify the Usability of the Snapshots by performing any of the above mentioned tests on the Snapshots
  1. Log in to the SSVM,
  2. Go to the directory where the secondary storage is mounted to.
  3. Go to the Snapshots directory on the secondary storage.
  4. Go to the account_id directory under Snapshots folder.
  5. xenserver only: Execute "vhd-util scan -p *.vhd".
  6. Output displays the chains of snapshots.
  7. Verify the Output.
  8. 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.
  9. Observe that the Snapshot is marked removed on the "snapshots" table.
 

NA

NANA

SP030

NA

Delete a Delta Snapshot present in the Chain of Snapshots

  1. Set the Snapshot.delta.max as 3
  2. Restart the Management Server
  3. Deploy a VM from the default Linux Template along with a data disk.
  4. Log into the VM and create a file on the ROOT disk with content in it.
  5. Create a Snapshot of the ROOT disk.
  6. Repeat Steps 4 and 5 at least six times
  7. Step 6 will generate at least two 'chains' of Snapshots on the Secondary Storage.
  8. The 1st ,4th ,7th ,10th ,....n+3 Snapshots are Full Snapshots of 'n' Snapshot chains.
  9. Remaining Snapshots other than the above mentioned Snapshots are Delta Snapshots.
  10. 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.
  11. Verify the Usability of the Snapshots by performing any of the above mentioned tests on the Snapshots
  1. Log in to the SSVM,
  2. Go to the directory where the secondary storage is mounted to.
  3. Go to the Snapshots directory on the secondary storage.
  4. Go to the account_id directory under Snapshots folder.
  5. xenserver only: Execute "vhd-util scan -p *.vhd".
  6. Output displays the chains of snapshots.
  7. Verify the Output.
  8. 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.
  9. Observe that the Snapshot is marked removed on the "snapshots" table.
 

NA

NANA

SP031

NA

Delete all the Snapshots present in the Chain of Snapshots

  1. Set the Snapshot.delta.max as 3
  2. Restart the Management Server
  3. Deploy a VM from the default Linux Template along with a data disk.
  4. Log into the VM and create a file on the ROOT disk with content in it.
  5. Create a Snapshot of the ROOT disk.
  6. Repeat Steps 4 and 5 at least six times
  7. Step 6 will generate at least two 'chains' of Snapshots on the Secondary Storage.
  8. Delete 1st, 2nd and 3rd Snapshots.
  9. Observe the entire chain of snapshots missing on the Secondary Storage.
  1. Log in to the SSVM,
  2. Go to the directory where the secondary storage is mounted to.
  3. Go to the Snapshots directory on the secondary storage.
  4. Go to the account_id directory under Snapshots folder.
  5. xenserver only: Execute "vhd-util scan -p *.vhd".
  6. Output displays the chains of snapshots.
  7. Verify the Output.
  8. 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

NANA

SP032

Try to create a Snapshot of a ROOT Volume of a Destroyed VM (Not expunged yet)

  1. This test need not be done if the Customer is not using Cloud Stack UI
  2. Deploy a VM from the Default Linux Template.
  3. Set the "expunge.interval" and "expunge.delay" to 900 seconds(15 mins)
  4. Restart the CloudStack Management Server.
  5. Destroy the VM.
  6. Using "createSnapshot" API, try to create a Snaphot of the ROOT Volume of the destroyed VM (not expunged yet).
  1. Snapshot Creation should Fail.
 

PASS

PASSPASS

SP033

When account is removed, all snapshots belonging to this account should be removed from Secondary Storage

  1. Create an account.
  2. Log in as the user of the account.
  3. Deploy a VM using the default Linux template.
  4. Create a Snapshot of the ROOT Volume of the VM.
  5. Repeat Steps 3 and 4, three times.
  6. Step 5 generates three Snapshots.
  7. Delete the Account.
  8. Observe that the snapshots are removed from the secondary storage.
  1. Before Snapshots Deletion, Verify the snapshots' entries in the "snapshots" table. Verify that they are not marked as removed.
  2. Verify the presence of the corresponding snapshots on the Secondary Storage
  3. After Deleting the Account, Verify the snapshots' entries of the corresponding Account are marked as removed in the "snapshots" table.
  4. Verify the absence of the corresponding snapshots on the Secondary Storage
 

PASS

PASSPASS

SP034

Create Snapshot of an Attached Volume

  1. Deploy a VM using the Default CentOS Template.
  2. Create a Volume.
  3. Attach the Volume to the VM deployed in Step 1.
  4. Log into the VM and create a ext3 file system on the Data Disk.
  5. Mount the Data Disk.
  6. Create a File with content on the Data Disk
  7. Create a Snapshot of the Data disk.
  1. Verify the snapshot's entry in the "snapshots" table.
  2. Verify the presence of the corresponding snapshot on the Secondary Storage
 

PASS

PASSPASS

SP035

Create Snapshot of a Detached Volume

  1. Deploy a VM using the Default CentOS Template.
  2. Create a Volume.
  3. Attach the Volume to the VM deployed in Step 1.
  4. Log into the VM and create a ext3 file system on the Data Disk.
  5. Mount the Data Disk.
  6. Create a File with content on the Data Disk
  7. Unmount the Data Disk from the VM.
  8. Create a Snapshot of the Data disk.
  1. Verify the snapshot's entry in the "snapshots" table.
  2. Verify the presence of the corresponding snapshot on the Secondary Storage
 

PASS

PASSPASS

SP036

Delete Snapshot of an Attached Volume

  1. Deploy a VM using the Default CentOS Template.
  2. Create a Volume.
  3. Attach the Volume to the VM deployed in Step 1.
  4. Log into the VM and create a ext3 file system on the Data Disk.
  5. Mount the Data Disk.
  6. Create a File with content on the Data Disk
  7. Create a Snapshot of the Data disk.
  8. Delete the Snapshot.
  9. Log into the VM and check the usability of the VM.
  1. Before Snapshot Deletion, Verify the snapshot's entry in the "snapshots" table. Verify that it is not marked as removed.
  2. Verify the presence of the corresponding snapshot on the Secondary Storage
  3. After Snapshot Deletion, Verify the snapshot's entry is marked as removed in the "snapshots" table.
  4. Verify the absence of the corresponding snapshot on the Secondary Storage
  5. Verify the Successful deployment of the VM.
  6. Log in and check the operational ability of the VM.
 

PASS

PASSPASS

SP037

Delete Snapshot of a Detached Volume

  1. Deploy a VM using the Default CentOS Template.
  2. Create a Volume.
  3. Attach the Volume to the VM deployed in Step 1.
  4. Log into the VM and create a ext3 file system on the Data Disk.
  5. Mount the Data Disk.
  6. Create a File with content on the Data Disk
  7. Unmount the Data Disk from the VM.
  8. Create a Snapshot of the Data disk.
  9. Delete the Snapshot.
  10. Log into the VM and check the usability of the VM.
  1. Before Snapshot Deletion, Verify the snapshot's entry in the "snapshots" table. Verify that it is not marked as removed.
  2. Verify the presence of the corresponding snapshot on the Secondary Storage
  3. After Snapshot Deletion, Verify the snapshot's entry is marked as removed in the "snapshots" table.
  4. Verify the absence of the corresponding snapshot on the Secondary Storage
  5. Verify the Successful deployment of the VM.
  6. Log in and check the operational ability of the VM.
 

PASS

PASSPASS

SP038

Create Hourly recurring snapshots for ROOT disk and data disks (limits, snapshot retention and auto deletion)

  1. Deploy a VM using the Default CentOS Template
  2. Create an Hourly Recurring snapshot policy on the ROOT disk.
  3. Observe the creation of a Snapshot after an hour.
  1. Verify the snapshot's entry in the "snapshots" table.
  2. Verify that the Snapshot's snapshot_type is HOURLY in the "snapshots" table.
  3. Verify the presence of the corresponding snapshot on the Secondary Storage
 

PASS

PASSPASS

SP039

Create Daily recurring snapshots for ROOT disk and data disks (limits, snapshot retention and auto deletion)

  1. Deploy a VM using the Default CentOS Template
  2. Create an Daily Recurring snapshot policy on the ROOT disk.
  3. Change the time on the host on which the management server is running***. Change the time to Current time + 23 hours.
  4. Restart the Management Server.
  5. Observe the creation of a Snapshot after an hour.
  6. ***Caution: Changing the Server time for the purpose of testing recurring snapshots might affect other time dependent features of CloudStack
  1. Verify the snapshot's entry in the "snapshots" table.
  2. Verify that the Snapshot's snapshot_type is DAILY in the "snapshots" table.
  3. Verify the presence of the corresponding snapshot on the Secondary Storage
 

PASS

 

PASSPASS

SP040

Create Weekly recurring snapshots for ROOT disk and data disks (limits, snapshot retention and auto deletion)

  1. Deploy a VM using the Default CentOS Template
  2. Create an Daily Recurring snapshot policy on the ROOT disk.
  3. Change the time on the host on which the management server is running***. Change the time to Current time + 6 Days + 23 hours.
  4. Restart the Management Server.
  5. Observe the creation of a Snapshot after an hour.
  6. ***Caution: Changing the Server time for the purpose of testing recurring snapshots might affect other time dependent features of CloudStack
  1. Verify the snapshot's entry in the "snapshots" table.
  2. Verify that the Snapshot's snapshot_type is WEEKLY in the "snapshots" table.
  3. Verify the presence of the corresponding snapshot on the Secondary Storage
 PASSPASSPASS

SP041

Create Monthly recurring snapshots for ROOT disk and data disks (limits, snapshot retention and auto deletion)

  1. Deploy a VM using the Default CentOS Template
  2. Create an Daily Recurring snapshot policy on the ROOT disk.
  3. 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.
  4. Restart the Management Server.
  5. Observe the creation of a Snapshot after an hour.
  6. ***Caution: Changing the Server time for the purpose of testing recurring snapshots might affect other time dependent features of CloudStack
  1. Verify the snapshot's entry in the "snapshots" table.
  2. Verify that the Snapshot's snapshot_type is MONTHLY in the "snapshots" table.
  3. Verify the presence of the corresponding snapshot on the Secondary Storage
 PASSPASSPASS
SP042while performing snapshot migrate ROOT volume to other primary storage
  1. Deploy a VM with data disk  using the Default CentOS Template
  2. Create additional primary storage
  3. 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

PASSPASS
SP043while performing snapshot migrate DATA volume to other primary storage
  1. Deploy a VM with data disk  using the Default CentOS Template
  2. Create additional primary storage
  3. 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 PASSPASSPASS
SP044create volume attach volume to VM
  1. create volume
  2. 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 casesSteps To Be Performed to TestVerification Steps rhel 6.3  
SP045VM sync- when snapshot in progress, kvm host "virsh list" shows VM  in "Paused" state
  1. Deploy a Linux VM using CentOS
  2. Perform snapshot on root disk ofVM
  3. 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

  
SP046As VM memory size increases, VM pause time increases during snapshot
  1. Deploy  Linux VMs using CentOS , memory size 512 MB to 16 GB same ROOT DATA disk size 20GB to 400 GB
  2. Perform snapshot on root & data disk of VM
  3. While snapshot in progress, on KVM host use "virsh list" to monitor VM pausetime
  4. 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
*

  
        
SP047Parallel snapshot for different VMs with large memory size on same host
  1. Deploy 5  Linux VMs memory 512 MB to 16 GB ROOT DATA disk size 20GB to 400 GB
  2. Perform parallel snapshot recurrrent scheduled root & data disk of VM
  3. While snapshot in progress, on KVM host use "virsh list" to monitor VM pausetime
  4. 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  
SP048In RHEL 6.5 when snapshot in progress kill snapshot process
  1. Deploy 5  Linux VMs using CentOS , memory size 512 MB to 16 GB same ROOT DATA disk size 20GB to 400 GB
  2. Perform snapshot on root & data disk of these VM of memory size.
  3. While snapshot in progress on KVM host, ps  -ef |  grep  ccp-qemu.img
  4. 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

 

  1. fresh install base OS rhel 6.3 CCP prior Goleta release.
  2. 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

  1. fresh install base OS rhel 6.3 CCP Goleta release.
  2. 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

  1. fresh install base OS rhel 6.4 CCP Goleta release.
  2. 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

  1. fresh install base OS rhel 6.5 CCP Goleta release.
  2. 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
  1. fresh install base OS rhel 6.3 CCP prior Goleta
  2. 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

  1. fresh install base OS rhel 6.3 CCP Goleta
  2. 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      
SP061automation:

smoke/test_snapshots.py

   PASSPASSPASS
SP062

automation:

component/test_recurring_snapshots.py

   some failsome failsome fail
SP063

automation:

component/test_snapshot_gc.py

   some failsome failsome fail
SP064automation:

component/test_snapshot_limits.py

   PASSPASSPASS
SP065automation:

component/test_snapshots.py

   some failsome failsome fail
SP066automation: component/test_snapshots_improvement.py   some failsome failsome fail
SP067automation: component/test_escalations_snapshots.py   some failsome failsome 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

  
        
        
        

 

 

*SP046  /var/log/cloudstack/agent/agent.log  message for snapshot pause time:

2014-09-02 17:19:29,280 DEBUG [cloud.agent.Agent] (agentRequest-Handler-3:null) Request:Seq 1-3962604722132615259:  { Cmd , MgmtId: 7203431909188, via: 1, Ver: v1, Flags: 100011, [{"org.apache.cloudstack.storage.command.CreateObjectCommand":{"data":{"org.apache.cloudstack.storage.to.SnapshotObjectTO":{"volume":{"uuid":"5a599331-8757-4d72-9b17-59afabbf77fd","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"45988504-2a99-3792-881a-5338c4ef1ad4","id":1,"poolType":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/angie/primary/kvmgo45","port":2049,"url":"NetworkFilesystem://10.223.110.232/export/home/angie/primary/kvmgo45/?ROLE=Primary&STOREUUID=45988504-2a99-3792-881a-5338c4ef1ad4"}},"name":"ROOT-8","size":8589934592,"path":"5a599331-8757-4d72-9b17-59afabbf77fd","volumeId":12,"vmName":"i-2-8-VM","accountId":2,"format":"QCOW2","provisioningType":"THIN","id":12,"deviceId":0,"hypervisorType":"KVM"},"dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"45988504-2a99-3792-881a-5338c4ef1ad4","id":1,"poolType":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/angie/primary/kvmgo45","port":2049,"url":"NetworkFilesystem://10.223.110.232/export/home/angie/primary/kvmgo45/?ROLE=Primary&STOREUUID=45988504-2a99-3792-881a-5338c4ef1ad4"}},"vmName":"i-2-8-VM","name":"z1512MD614GV14_ROOT-8_20140903001930","hypervisorType":"KVM","id":301,"quiescevm":false,"physicalSize":0}},"wait":0}}] }

2014-09-02 17:19:29,281 DEBUG [cloud.agent.Agent] (agentRequest-Handler-3:null) Processing command: org.apache.cloudstack.storage.command.CreateObjectCommand

2014-09-02 17:19:29,287 DEBUG [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-3:null) Trying to fetch storage pool 45988504-2a99-3792-881a-5338c4ef1ad4 from libvirt

2014-09-02 17:19:29,654 DEBUG [kvm.storage.LibvirtStorageAdaptor] (agentRequest-Handler-3:null) Trying to fetch storage pool 45988504-2a99-3792-881a-5338c4ef1ad4 from libvirt

 

2014-09-02 17:19:30,582 DEBUG [kvm.storage.KVMStorageProcessor] (agentRequest-Handler-5:null) snapshot takes 40 seconds to finish

 

2014-09-02 17:19:30,588 DEBUG [cloud.agent.Agent] (agentRequest-Handler-5:null) Seq 1-3962604722132615253:  { Ans: , MgmtId: 7203431909188, via: 1, Ver: v1, Flags: 10, [{"org.apache.cloudstack.storage.command.CreateObjectAnswer":{"data":{"org.apache.cloudstack.storage.to.SnapshotObjectTO":{"path":"/mnt/45988504-2a99-3792-881a-5338c4ef1ad4/65213262-a70b-4e99-9050-d250071f4437/b63a0b5b-d23a-44c7-8295-74e2a04a7e87","id":0,"quiescevm":false,"physicalSize":0}},"result":true,"wait":0}}] }

2014-09-02 17:19:30,965 DEBUG [cloud.agent.Agent] (agentRequest-Handler-2:null) Request:Seq 1-3962604722132615260:  { Cmd , MgmtId: 7203431909188, via: 1, Ver: v1, Flags: 100011, [{"org.apache.cloudstack.storage.command.CopyCommand":{"srcTO":{"org.apache.cloudstack.storage.to.SnapshotObjectTO":{"path":"/mnt/45988504-2a99-3792-881a-5338c4ef1ad4/65213262-a70b-4e99-9050-d250071f4437/b63a0b5b-d23a-44c7-8295-74e2a04a7e87","volume":{"uuid":"65213262-a70b-4e99-9050-d250071f4437","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"45988504-2a99-3792-881a-5338c4ef1ad4","id":1,"poolType":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/angie/primary/kvmgo45","port":2049,"url":"NetworkFilesystem://10.223.110.232/export/home/angie/primary/kvmgo45/?ROLE=Primary&STOREUUID=45988504-2a99-3792-881a-5338c4ef1ad4"}},"name":"ROOT-4","size":8589934592,"path":"65213262-a70b-4e99-9050-d250071f4437","volumeId":5,"vmName":"i-2-4-VM","accountId":2,"format":"QCOW2","provisioningType":"THIN","id":5,"deviceId":0,"hypervisorType":"KVM"},"parentSnapshotPath":"/mnt/45988504-2a99-3792-881a-5338c4ef1ad4/65213262-a70b-4e99-9050-d250071f4437/1853272f-8131-4e6a-94e2-17c70ca959a3","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"45988504-2a99-3792-881a-5338c4ef1ad4","id":1,"poolType":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/angie/primary/kvmgo45","port":2049,"url":"NetworkFilesystem://10.223.110.232/export/home/angie/primary/kvmgo45/?ROLE=Primary&STOREUUID=45988504-2a99-3792-881a-5338c4ef1ad4"}},"vmName":"i-2-4-VM","name":"z112GD400GV11_ROOT-4_20140903001849","hypervisorType":"KVM","id":299,"quiescevm":false,"parents":["/mnt/45988504-2a99-3792-881a-5338c4ef1ad4/65213262-a70b-4e99-9050-d250071f4437/1853272f-8131-4e6a-94e2-17c70ca959a3"],"physicalSize":0}},"destTO":{"org.apache.cloudstack.storage.to.SnapshotObjectTO":{"path":"snapshots/2/5","volume":{"uuid":"65213262-a70b-4e99-9050-d250071f4437","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"45988504-2a99-3792-881a-5338c4ef1ad4","id":1,"poolType":"NetworkFilesystem","host":"10.223.110.232","path":"/export/home/angie/primary/kvmgo45","port":2049,"url":"NetworkFilesystem://10.223.110.232/export/home/angie/primary/kvmgo45/?ROLE=Primary&STOREUUID=45988504-2a99-3792-881a-5338c4ef1ad4"}},"name":"ROOT-4","size":8589934592,"path":"65213262-a70b-4e99-9050-d250071f4437","volumeId":5,"vmName":"i-2-4-VM","accountId":2,"format":"QCOW2","provisioningType":"THIN","id":5,"deviceId":0,"hypervisorType":"KVM"},"parentSnapshotPath":"snapshots/2/5/1853272f-8131-4e6a-94e2-17c70ca959a3","dataStore":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.223.110.232/export/home/angie/secondary/kvmgo45","_role":"Image"}},"vmName":"i-2-4-VM","name":"z112GD400GV11_ROOT-4_20140903001849","hypervisorType":"KVM","id":299,"quiescevm":false,"parents":["snapshots/2/5/1853272f-8131-4e6a-94e2-17c70ca959a3"],"physicalSize":0}},"executeInSequence":false,"options":{"fullSnapshot":"true"},"wait":21600}}] }

 

 

  • No labels