[
https://issues.apache.org/jira/browse/CLOUDSTACK-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ram Ganesh updated CLOUDSTACK-458:
----------------------------------
Assignee: (was: deepti dohare)
> xen:snapshots:Storage gc fail to clean the failed snapshot images from
> secondarystorage
> ---------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-458
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-458
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Snapshot
> Affects Versions: 4.0.0
> Reporter: deepti dohare
> Priority: Minor
> Fix For: 4.3.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
