[CLOUDSTACK-458] xen:snapshots:Storage gc fail to clean the failed snapshot images from secondarystorage

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 4.0.0
• Component/s: Snapshot
• Security Level: Public (Anyone can view this level - this is the default.)
• Assignee: Disheng Su
• Reporter: deepti dohare
• Created: 08/Nov/12 13:23
• Updated: 17/Mar/17 19:27
• Resolved: 17/Mar/17 19:27

Description

After storage cleanup still see the snapshot image oin the secondary storage snapshot folder for the failure snapshots
In this case : next hourly snapshot was successful but previous snapshot was stuck in backingupstate....

Steps:

• • • • • • • • • • • • • • • 1.Deploy a VM and set concurrent.snapshots.threshold.per host to 2
                              2.Once its successful,schedule the recurring snapshots hourly on the root volume and also perform snapshot on other instance volumes
                              3.configure the storage.cleanup.interval to 150 and restart the cloud-management service while hourly snapshot on root volume is in progress

4.check the secondary storage snapshot folder
5. after few hours,delete all the created snapshots from Cloudstack and check the storage cleanup thread cleansup all the snapshots form the snapshot folder or not.

Actual result:
step4:snapshots job failed and secondary storage has copied image file and database shows snapshot job status as "Backing UP"

next hourly snapshot was successful.

Step5:
It cleans all the successful hourly snapshot images except the failed snapshot image files

Expected result:

• • • • • • • • • • • • • • • • • • 
                                    Storage GC should clean all image files exists in the snapshot folder when we delete the all the snapshots from Cloud stack.

also when previous hourly snapshot stuck in backing up state ,the next hourly snapshot is successful,Cloudstack should intelligent enough to update the status of failure jobs properly.