Page History

1. Deploy a Linux VM using default CentOS template, use small service offering, disk offering

1. Log into the VM and create a file with content in it.
2. 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

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

1. Log into the VM and create a file on the desktop with content in it

1. .

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

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

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.

1. Verify the presence of the corresponding snapshot on

1. the Secondary Storage

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.

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.

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

1. 's entry in the "

1. template_host_ref" table.

2. Verify the presence of the corresponding template on the Secondary Storage

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

1. Secondary Storage

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.

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

1. of a Windows VM.

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

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.

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

1. Snapshot of a ROOT Volume of a

1. Windows VM.

1. Log in and check the operational ability of the VM.

1. Before Snapshot Deletion, Verify the snapshot's entry in the "

1. snapshots" table

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

SP013

Create

Volume from a Snapshot of a ROOT disk

of a Linux VM.

1. Create a Snapshot of a ROOT

1. Disk of a Linux VM.

1. Create a Volume from the Snapshot.

1. Verify the

1. snapshot's entry in the "

1. snapshots" table

1. .

1. Verify the presence of the corresponding

1. snapshot on the

1. Secondary Storage

1. .
2. Verify the Volume's entry in the "Volume" table.
3. Verify the presence of the corresponding volume on the Secondary Storage.

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.

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

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

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

1. Secondary Storage

1. .
2. Verify the Volume's entry in the "Volume" table.
3. Verify the presence of the corresponding volume on the Secondary Storage.
4. Steps need to be provided.

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

1. 's entry in the "

1. Volume" table.

2. Verify the presence of the corresponding volume on the Secondary Storage.
3. Log into the VM and observe the existence of the new Volume under /dev

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

1. Disk of a Windows VM.

1. Create a Volume from the Snapshot.
2. Deploy a Windows VM from a different Windows Template.
3. Attach the Volume to the newly created Linux VM.

1. Verify the snapshot's entry

1. in the "snapshots" table.

1. Verify the

1. presence of the corresponding snapshot on the

1. Secondary Storage

1. .
2. Verify the Volume's entry in the "Volume" table.
3. Verify the presence of the corresponding volume on the Secondary Storage.
4. Steps need to be provided.

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.

1. Create a

1. Volume from the Snapshot.
2. Attach the Volume to the Same Linux VM.

1. Detach the Attached Volume.

1. Verify the snapshot's entry in the "snapshots" table

1. .

1. Verify the presence of the corresponding snapshot on the

1. Secondary Storage.

1. Verify the Volume's entry in the "Volume" table.

1. Verify the presence of the corresponding volume on the

1. Secondary Storage.

1. Log into the VM and observe the existence of the new Volume under /dev
2. After detaching the Volume, Log into the VM and observe the non-existence of the new Volume under /dev

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.

2. Attach the Volume to the Same Windows VM
3. Detach the Attached Volume.

1. Verify the snapshot's entry in the "snapshots" table

1. .

1. Verify the presence of the corresponding snapshot on the

1. Secondary Storage.
2. Verify the Volume's entry in the "Volume" table.
3. Verify the presence of the corresponding volume on the Secondary Storage.

1. Steps need to be provided.

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

1. Secondary Storage.

1. Verify the Volume's entry in the "Volume" table.

1. Verify the presence of the corresponding volume on the

1. Secondary Storage.

1. Log into the VM and observe the existence of the new Volume under /dev
2. After detaching the Volume, Log into the VM and observe the non-existence of the new Volume under /dev

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

1. Windows VM.

1. Create a Volume from the Snapshot.
2. Deploy a Windows VM from a different Windows Template.
3. Attach the Volume to the newly created Linux VM.
4. Detach the Attached Volume.

1. Verify the snapshot's entry in the "snapshots" table

1. .

1. Verify the presence of the corresponding snapshot on the

1. Secondary Storage.

1. Verify the Volume's entry in the "Volume" table.

1. Verify the presence of the corresponding volume on the

1. Secondary Storage.

1. Steps need to be provided.

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

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

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

NA

Create a Chain of Snapshots of a Data disk of a

Linux VM

that resides on a ESXi 4.0 Host

SP023

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 Output

SP024

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

SP025

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.

SP026

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.

SP027

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.

SP028

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.

SP029

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

SP030

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

SP031

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

SP032

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.

1. Verify that it is not marked as removed.

1. Verify the presence of the corresponding snapshot on the

1. Secondary Storage

2. After Snapshot Deletion, Verify the snapshot's entry is marked as removed in the "snapshots" table.
3. Verify the absence 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.

SP033

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.

1. Verify that it is not marked as removed.

1. Verify the presence of the corresponding snapshot on the

1. Secondary Storage

2. After Snapshot Deletion, Verify the snapshot's entry is marked as removed in the "snapshots" table.
3. Verify the absence 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

1. .

SP034

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

NA

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

NA

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

NA

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

Upgrade

rhel6.2  3.0.7 -> 

rhel6.5  4.5

1. baseOS rhel6.2 MS  3.0.7 patchF upgrade to baseOS rhel6.5 MS  4.5

Upgrade 

rhel6.3  4.2.1 -> 

rhel6.5  4.5

1. baseOS rhel6.3 MS  4.2.1              upgrade to baseOS rhel6.5 MS  4.5

Upgrade

rhel6.3  4.3.0.1 ->  rhel6.5  4.5

1. baseOS rhel6.3 MS   4.3.0.1           upgrade to baseOS rhel6.5 MS  4.5

Upgrade 

rhel6.4  4.2.1 -> 

rhel6.5  4.5

1. baseOS rhel6.4 MS  4.2.1               upgrade to baseOS rhel6.5 MS  4.5

Upgrade

rhel6.4  4.3.0.1 ->  rhel6.5  4.5

1. baseOS rhel6.4 MS  4.3.0.1           upgrade to baseOS rhel6.5 MS  4.5

Upgrade 

rhel6.3  4.2.1 -> 

rhel6.3  4.5

1. baseOS rhel6.3 MS  4.2.1              upgrade to baseOS rhel6.3 MS  4.5

Upgrade 

rhel6.3  4.3.0.1 -> 

rhel6.3  4.5

1. baseOS rhel6.3 MS  4.3.0.1           upgrade to baseOS rhel6.3 MS  4.5