Versions Compared

Old Version 6

changes.mady.by.user angie shen

Saved on

compared with

New Version Current

changes.mady.by.user angie shen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0
 

Test ID

Test Case Name

Steps

Expected Results

Priority

Testcase Type(SANITY | FUNCTIONAL)

Result

 

 

 

 

 

 

 

 

 

 

 

 

 

 

KVM.snapshot.enabled=TRUE

 

 

 

 

 

 

 

SP001  

Take snapshot on root disk

  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

P1

FUNCTIONAL

https://issues.apache.org/jira/browse/CLOUDSTACK-2468 
blocker - fixed

http://bugs-ccp.citrix.com/browse/CS-17970
fixed
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

P1

FUNCTIONAL Pass

http://bugs-ccp.citrix.com/browse/CS-17970
fixed
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

P1

FUNCTIONAL Pass

http://bugs-ccp.citrix.com/browse/CS-17970
fixed
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

P1

FUNCTIONAL

 

 

 

http://bugs-ccp.citrix.com/browse/CS-17970
fixed
PASS

 

 

SP005

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.

P1

FUNCTIONAL

PASS Pass

 

 

SP005

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.

P1

FUNCTIONAL

Pass

 

 

SP006

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. <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="055d760b-2d56-48d6-a3ab-272632ac794d"><ac:plain-text-body><![CDATA[#
  2. Verify the presence of the corresponding template on the Secondary Storage

P1

FUNCTIONAL

[httpshttp://issuesbugs-ccp.apachecitrix.org/jiracom/browse/CS-17719
fixed
blocked by   
 http://bugs-ccp.citrix.com/browse/CLOUDSTACK-2499 httpsCS-17970 
fixed
blocked by
http://issuesbugs-ccp.apachecitrix.org/jiracom/browse/CLOUDSTACK-2499
]]></ac:plain-text-body></ac:structured-macro>
]
Fail
CS-17989
FAIL

[

[http://bugs-ccp.citrix.com/browse/CS-17719]]

 

 

SP007

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. <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="33665db2-a48e-4a98-8f57-0c487bfd37d6"><ac:plain-text-body><![CDATA[# Verify the
  2. Verify the presence of the corresponding template on the Secondary Storage

P1

 

[httpshttp://issuesbugs-ccp.apachecitrix.org/jiracom/browse/CLOUDSTACK-2499 httpsCS-17719
fixed
blocked by    
 http://issuesbugs-ccp.apachecitrix.org/jiracom/browse/CS-17970
fixed
blocked by
http://bugs-ccp.citrix.com/browse/CLOUDSTACK-2499
]]></ac:plain-text-body></ac:structured-macro>
]
Fail
CS-17989
FAIL

[

[http://bugs-ccp.citrix.com/browse/CS-17719]]

 

 

SP008

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.

P1

 

<ac

http:

structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="5333da37-fdf6-454d-9b48-648cffaab42e"><ac:plain-text-body><![CDATA[# Log in and check the operational ability of the VM.

P1

 

[https://issues.apache.org/jira/browse/CLOUDSTACK-2499

//bugs-ccp.citrix.com/browse/CS-17719
fixed
blocked by
 http://bugs-ccp.citrix.com/browse/CS-17970
fixed
blocked by
http://bugs-ccp.citrix.com/browse/CS-17989
FAIL

[

[http://bugs-ccp.citrix.com/browse/CS-17719]] https://issues.apache.org/jira/browse/CLOUDSTACK-2499
]]></ac:plain-text-body></ac:structured-macro>
]

 

 

SP009

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.

P1

 

<ac

http:

structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="9b1a56a8-73b5-4a88-8bc7-8eea5121f895"><ac:plain-text-body><![CDATA[# Log in and check the operational ability of the VM.

P1

 

[https://issues.apache.org/jira/browse/CLOUDSTACK-2499

//bugs-ccp.citrix.com/browse/CS-17719
fixed
blocked by
 http://bugs-ccp.citrix.com/browse/CS-17970
fixed
blocked by
http://bugs-ccp.citrix.com/browse/CS-17989
FAIL

[

[http://bugs-ccp.citrix.com/browse/CS-17719]] https://issues.apache.org/jira/browse/CLOUDSTACK-2499
]]></ac:plain-text-body></ac:structured-macro>
]

 

 

SP010

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.

P2

 

<ac

http:

structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="60073a09-48dc-473a-80ef-d1a0d56d2f83"><ac:plain-text-body><![CDATA[# Log in and check the operational ability of the VM.

P2

 

[https://issues.apache.org/jira/browse/CLOUDSTACK-2499

//bugs-ccp.citrix.com/browse/CS-17719
fixed
blocked by
 http://bugs-ccp.citrix.com/browse/CS-17970
fixed
blocked by
http://bugs-ccp.citrix.com/browse/CS-17989
FAIL

[

[http://bugs-ccp.citrix.com/browse/CS-17719] https://issues.apache.org/jira/browse/CLOUDSTACK-2499
]]></ac:plain-text-body></ac:structured-macro>
]

 

 

SP011

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.

P2

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="a2437979-2e14-4884-b8b9-07e59fb3fe88"><ac:plain-text-body><![CDATA[# Log in and check the operational ability of the VM.

P2

 

[https://issues.apache.org/jira/browse/CLOUDSTACK-2499

 

http://bugs-ccp.citrix.com/browse/CS-17719
fixed
blocked by
http://bugs-ccp.citrix.com/browse/CS-17970
fixed
blocked by
http://bugs-ccp.citrix.com/browse/CS-17989
FAIL

[

[http://bugs-ccp.citrix.com/browse/CS-17719] https://issues.apache.org/jira/browse/CLOUDSTACK-2499
]]></ac:plain-text-body></ac:structured-macro>
]

 

 

SP012

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.

P1

 

[httpshttp://issuesbugs-ccp.apache.org/jiracitrix.com/browse/CS-17720
fixed
blocked by
http://bugs-ccp.citrix.com/browse/CLOUDSTACKCS-2500] 17970
Fail fixed

 

 

SP013

blocked by
 http://bugs-ccp.citrix.com/browse/CS-17988
FAIL

 

 

SP013

Create 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.

P1

 

[httpshttp://issuesbugs-ccp.apachecitrix.orgcom/jira/browse/CLOUDSTACK-2500]
Fail

 

 

CS-17720
fixed
blocked by
http://bugs-ccp.citrix.com/browse/CS-17970
fixed
blocked by
http://bugs-ccp.citrix.com/browse/CS-17988
FAIL

 

 

SP014

Attach the Volume created from the Snapshot of a

SP014

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

P1

 

[httpshttp://issuesbugs-ccp.apache.org/jiracitrix.com/browse/CS-17720
fixed
blocked by
http://bugs-ccp.citrix.com/browse/CLOUDSTACKCS-2500] 17970
  fixed

 

blocked by
http://bugs-ccp.citrix.com/browse/CS-17988
FAIL

[

[http://bugs-ccp.citrix.com/browse/CS-17720]]

 

SP015

Attach the Volume created from the Snapshot of

SP015

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.

P1

 

httpshttp://issuesbugs-ccp.apache.org/jiracitrix.com/browse/CS-17720
fixed
blocked by http://bugs-ccp.citrix.com/browse/CLOUDSTACKCS-250017970

 

fixed
blocked by
http://bugs-ccp.citrix.com/browse/CS-17988
FAIL

 

 

SP016

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

P2

 

httpshttp://issuesbugs-ccp.apache.org/jiracitrix.com/browse/CS-17720
fixed
blocked by
http://bugs-ccp.citrix.com/browse/CLOUDSTACKCS-250017988
FAIL

 

 

SP017

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.

P2

  

http://bugs-ccp.citrix.com/browse/CS-17988
FAIL

 

 

SP018

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

P1

 

httpshttp://issuesbugs-ccp.apache.org/jiracitrix.com/browse/CS-17720
fixed
blocked by
http://bugs-ccp.citrix.com/browse/CLOUDSTACKCS-250017988
FAIL

 

 

SP019

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.

P1

 

httpshttp://issuesbugs-ccp.apache.org/jiracitrix.com/browse/CS-17720
http://bugs-ccp.citrix.com/browse/CLOUDSTACKCS-250017970
  fixed

 

blocked by

http://bugs-ccp.citrix.com/browse/CS-17988
FAIL

 

 

SP020

Detach the Attached Volume. The

SP020

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

P2 P1

 

http://bugs-ccp.citrix.com/browse/CS-17720
httphttps://issuesbugs-ccp.apache.org/jiracitrix.com/browse/CS-17970
fixed
blocked by

http://bugs-ccp.citrix.com/browse/CLOUDSTACKCS-250017988
FAIL

 

 

SP021

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.

P2

 

 

http://bugs-ccp.citrix.com/browse/CS-17988
FAIL 

 

 

SP022

Create a Chain of Snapshots of a ROOT disk of a Linux VM that resides on a Xenserver 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. Execute "vhd-util scan -p *.vhd".-XEN only
  6. Output displays the chains of snapshots.
  7. Verify the Output

P1

  

PASS

 

 

SP023

Create a Chain of Snapshots of a Data disk of a Linux VM that resides on a Xenserver 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. Execute "vhd-util scan -p *.vhd" .- XEN only
  6. Output displays the chains of snapshots.
  7. Verify the Output

P2

  

PASS

 

 

SP024 SP028

Create Delete a Full Snapshot present in the Chain of Snapshots of a ROOT disk of a Linux VM that resides on a ESXi 4.0 Host

Presently Chain of Snapshots is not supported. Every Snapshot of a Volume of a VM residing on an ESXi host is a Full Snapshot. Feature will be supported in Bonita

 

 

 

 

 

 

SP025

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

Presently Chain of Snapshots is not supported. Every Snapshot of a Volume of a VM residing on an ESXi host is a Full Snapshot. Feature will be supported in Bonita

 

 

 

 

 

 

SP026

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

Presently Chain of Snapshots is not supported. Every Snapshot of a Volume of a VM residing on an ESXi host is a Full Snapshot. Feature will be supported in Bonita

 

 

 

 

 

 

SP027

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

Presently Chain of Snapshots is not supported. Every Snapshot of a Volume of a VM residing on an ESXi host is a Full Snapshot. Feature will be supported in Bonita

 

 

 

 

 

 

  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. Execute "vhd-util scan -p *.vhd"-XEN only
  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.

P1

PASS

http://bugs-ccp.citrix.com/browse/CS-17971
fixed
PASS

 

 

SP029

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

SP028

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. Remaining Snapshots other than the above mentioned Snapshots are Delta Snapshots.
  10. Delete (i+1)th Full Snapshot and Delta Snapshot where (i)th Snapshot is a Full Snapshot and (i+2)th Snapshot is a Delta Snapshot. Verify the Usability of (i+1)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. Execute "vhd-util scan -p *.vhd" .- XEN only
  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.

P1

  

http://bugs-ccp.citrix.com/browse/CS-17971
fixed
PASS

 

 

SP029 SP030

Delete a Delta Snapshot 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. The Delete 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
  12. 2nd and 3rd Snapshots.
  13. 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. Log in to the SSVM,
  5. Go to the directory where the secondary storage is mounted to.
  6. Go to the Snapshots directory on the secondary storage.
  7. Go to the account_id directory under Snapshots folder.
  8. Execute "vhd-util scan -p *.vhd" .- XEN only
  9. Output displays the chains of snapshots.
  10. Verify the Output.
  11. Execute Step 5 after Snapshot Deletion and check the existence of the deleted Snapshot in the chain. The Snapshot is not deleted deleting all the snapshots present in a chain. The chain should no longer exist 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. All snapshots belonging to the chain should be missing on the secondary storage.

P1

  

http://bugs-ccp.citrix.com/browse/CS-17971
fixed
PASS

 

 

SP030

Delete all the Snapshots present in the Chain of Snapshots

SP031

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. Set the Snapshot.delta.max as 3
  3. Restart the Management Server
  4. Deploy a VM from the default Default Linux Template along with a data disk.
  5. Log into the VM and create a file on the ROOT disk with content in it.
  6. Create a Snapshot of the ROOT disk.
  7. Repeat Steps 4 and 5 at least six times
  8. Step 6 will generate at least two 'chains' of Snapshots on the Secondary Storage.
  9. Delete 1st, 2nd and 3rd Snapshots.
  10. 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. 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.

P1

 

 

 

 

SP031

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.

P3

 

 

 

 

  1. Set the "expunge.interval" and "expunge.delay" to 900 seconds(15 mins)
  2. Restart the CloudStack Management Server.
  3. Destroy the VM.
  4. Using "createSnapshot" API, try to create a Snaphot of the ROOT Volume of the destroyed VM (not expunged yet).
  1. Snapshot Creation should Fail.

P1


PASS

 

 

SP032

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

P1

Pass

PASS

 

 

SP033

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

P1


PASS

 

 

SP034

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

SP032

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 presence of the corresponding snapshots snapshot on the Secondary Storage

P1


  PASS

 

  

SP035

SP033

Create 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

P2

 

 

 

 

SP034

Create Snapshot of a Detached Volume

  1. After Snapshot Deletion, Verify the snapshot's entry is marked as removed in the "snapshots" table.
  2. Verify the absence of the corresponding snapshot on the Secondary Storage
  3. Verify the Successful deployment of the VM.
  4. Log in and check the operational ability of the VM.

P1

 

PASS

 

 

SP036

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
  4. Deploy a VM using the Default CentOS Template.
  5. Create a Volume.
  6. Attach the Volume to the VM deployed in Step 1.
  7. Log into the VM and create a ext3 file system on the Data Disk.
  8. Mount the Data Disk.
  9. Create a File with content on the Data Disk
  10. Unmount the Data Disk from the VM.
  11. Create a Snapshot of the Data disk.
  12. Delete the Snapshot.
  13. 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

P2

 

 

 

 

SP035

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. After Snapshot Deletion, Verify the snapshot's entry is marked as removed in the "snapshots" table.
  2. Verify the absence of the corresponding snapshot on the Secondary Storage
  3. Verify the Successful deployment of the VM.
  4. Log in and check the operational ability of the VM.

P1


http://bugs-ccp.citrix.com/browse/CS-17971
fixed
PASS

 

 

SP037

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. Before Snapshot Deletion, Verify the snapshot's entry in the "snapshots" table.
  2. Verify that it is not marked as removed.Verify the presence of the corresponding snapshot on the Secondary StorageAfter Snapshot Deletion, Verify the snapshot's entry is marked as removed snapshot_type is HOURLY in the "snapshots" table.
  3. Verify the absence presence of the corresponding snapshot on the Secondary Storage
  4. Verify the Successful deployment of the VM.
  5. Log in and check the operational ability of the VM.

P2

P1

 

http://bugs-ccp.citrix.com/browse/CS-18004
FAIL

 

 

SP038

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

 

 

 

 

SP036

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.
  11. an Daily Recurring snapshot policy on the ROOT disk.
  12. Change the time on the host on which the management server is running***. Change the time to Current time + 23 hours.
  13. Restart the Management Server.
  14. Observe the creation of a Snapshot after an hour.
  15. ***Caution: Changing the Server time for the purpose of testing recurring snapshots might affect other time dependent features of CloudStack
  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
  4. Verify that the Snapshot's snapshot_type is DAILY After Snapshot Deletion, Verify the snapshot's entry is marked as removed in the "snapshots" table.
  5. Verify the absence presence of the corresponding snapshot on the Secondary Storage
  6. Verify the Successful deployment of the VM.
  7. Log in and check the operational ability of the VM.

P1

 

http://bugs-ccp.citrix.com/browse/CS-18004
FAIL P2

 

 

 

 

SP037 SP039

Create Hourly 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 Hourly 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 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 HOURLY WEEKLY in the "snapshots" table.
  3. Verify the presence of the corresponding snapshot on the Secondary Storage

P1

  

http://bugs-ccp.citrix.com/browse/CS-18004
FAIL

 

 

SP038 SP040

Create Daily 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 DAILY MONTHLY in the "snapshots" table.
  3. Verify the presence of the corresponding snapshot on the Secondary Storage

P1

 

http://bugs-ccp.citrix.com/browse/CS-18004
FAIL

 

  

SP041

SP039

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

volume migration
ROOT volume

1. Add primary storage
2. stop instance
3. perform volume migration of root volume of instance

1. Add primary storage
2. stop instance
3. perform volume migration of root volume of instance

volume migration of instance root volume  should succeed
 

P1

FUNCTIONAL

PASS

  P1

 

 

 

 

SP040

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

KVM.snapshot.enabled=FALSE

 

 

 

 

 

SP043

Create an Hourly

  • 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

    • disk

    Verify  snapshot cannot be created for root disk or data disk

     

    P1

    FUNCTIONAL

    http://bugs-ccp.citrix.com/browse/CS-17972
    FAIL

     

     

     

     

     

     

    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

    P1

     

     

     

     

    SP041 

    volume migration  ROOT volume

    1. Add primary storage
    2. stop instance
    3. perform volume migration of root volume of instance

    1. Add primary storage
    2. stop instance
    3. perform volume migration of root volume of instance

    P1

    FUNCTIONAL

    volume migration of instance root volume  should succeed

     

     

     

     

     

     

     

     

     

     

     

     

     

    KVM.snapshot.enabled=FALSE

     

     

     

     

     

     

     

     

     

     

     

     

     

     

    PASS

     

     

    SP042

    take snapshot on root disk and data disk

    1. Log into the VM and create a file with content in it.
    2. Deploy a Linux VM using default CentOS template, use small service offering, disk offering
    3. Perform snapshot on the root disk and data disk of this newly created VM |
    1. Verify snapshot cannot be taken for root disk and data dis | Verify  snapshot cannot be created for root disk or data disk | P1
      | FUNCTIONAL
      | PASS
      | | |

      SP043

      recurring snapshot on root disk and data disk

      1. Deploy a VM using the Default CentOS Template
    2. Create an Hourly Recurring snapshot policy on the ROOT disk. | Verify  recurring snapshot cannot be created for root disk or data disk | P1
      | FUNCTIONAL
      | FAIL
      | | |

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

      SP042

      take snapshot on root disk and data disk

    3. Log into the VM and create a file with content in it.
    4. Deploy a Linux VM using default CentOS template, use small service offering, disk offering
    5. Perform snapshot on the root disk and data disk of this newly created VM |
    6. Verify snapshot cannot be taken for root disk and data disk | P1 | FUNCTIONAL | PASS | | |

      SP043

      recurring snapshot for root disk and data disk

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

    7. Verify recurring snapshot cannot be scheduled for root disk or data disk | P1 | FUNCTIONAL | FAIL | | |

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

    Test Cases:

    1. Create a Snapshot of a RootDisk of a VM while in running, stopped and transition states
    2. Create a Snapshot of a DataDisk of a VM (running, stopped and transition states).
    3. Generate event when snapshot gets created/deleted  (root disks and data disks)
    4. Try to create a snapshot for Destroyed volume - Negative case
    5. Creating snapshot should reflect in the system wide capacity on the DashBoard
    6. Deleting snapshot should reflect in the system wide capacity on the DashBoard
    7. When account is removed, all snapshots belonging to this account should be removed from Secondary Storage
    8. Delete snapshot created from Attached/Detached volumes
    9. create snapshot from a detached volume
    10. create/attach/detach/delete volumes from snapshots created from an attached volume (VM in start, stop and transition states)
    11. hourly recurring snapshots for root disk and data disks (limits, snapshot retention and auto deletion)
    12. daily recurring snapshots for root disk and data disks  (limits, snapshot retention and auto deletion)
    13. weekly recurring snapshots for root disk and data disks  (limits, snapshot retention and auto deletion)
    14. monthly recurring snapshots for root disk and data disks  (limits, snapshot retention and auto deletion)
    15. create manual snapshot of the root disk of a VM created form ISO image
    16. Create a Volume from a snapshot of a rootdisk
    17. Create a Volume from a snapshot of a datadisk
    18. Attach Volume  created from a snapshot to the parent VM
    19. Attach Volume created from a snapshot to a different VM
    20. Create a template from a snapshot
    21. Create a VM from a snapshot template
    22. Stop, Start, Reboot, Destroy the VM created from a snapshot
    23. Create more than one VM from a snapshot
    24. Reboot and snapshot at the same time
    25. Test the dependency between a sequence of snapshots of a particular volume
    26. Delete the snapshots in the middle of a sequence and see that the final snapshot is not affected