[
https://issues.apache.org/jira/browse/CLOUDSTACK-9572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16579068#comment-16579068
]
ASF GitHub Bot commented on CLOUDSTACK-9572:
--------------------------------------------
mike-tutkowski commented on issue #1740: CLOUDSTACK-9572 Snapshot on primary
storage not cleaned up after Stor…
URL: https://github.com/apache/cloudstack/pull/1740#issuecomment-412712008
I should have placed these comments here (in GitHub) and let them propagate
to JIRA. I'm going to copy/paste the relevant comments I made in JIRA here:
Comment:
After updating master on my local repo, I can no longer reproduce the issue
I described above. With 46c56ea, the workflow behaves as expected. It would
seem there was an issue in a previous version of master, but that it no longer
exists.
Comment:
With regards to your snapshot-delete question:
As far as I know, if you migrate a volume from one primary storage to
another, there should never exist any primary storage-based snapshots of this
volume after the migration has taken place. That being the case, I don't think
you should get back primary storage-based snapshots from
snapshotFactory.getSnapshots that are from different primary storages.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Snapshot on primary storage not cleaned up after Storage migration
> ------------------------------------------------------------------
>
> Key: CLOUDSTACK-9572
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9572
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
> Affects Versions: 4.8.0
> Environment: Xen Server
> Reporter: subhash yedugundla
> Priority: Major
> Fix For: 4.8.1
>
>
> Issue Description
> ===============
> 1. Create an instance on the local storage on any host
> 2. Create a scheduled snapshot of the volume:
> 3. Wait until ACS created the snapshot. ACS is creating a snapshot on local
> storage and is transferring this snapshot to secondary storage. But the
> latest snapshot on local storage will stay there. This is as expected.
> 4. Migrate the instance to another XenServer host with ACS UI and Storage
> Live Migration
> 5. The Snapshot on the old host on local storage will not be cleaned up and
> is staying on local storage. So local storage will fill up with unneeded
> snapshots.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
