andrijapanicsb opened a new issue #3646: Garbage snapshots are left on Primary and Secondary storage after a volume snapshot is deleted URL: https://github.com/apache/cloudstack/issues/3646 ##### ISSUE TYPE <!-- Pick one below and delete the rest --> * Bug Report ##### COMPONENT NAME <!-- Categorize the issue, e.g. API, VR, VPN, UI, etc. --> ~~~ snapshots handling ~~~ ##### CLOUDSTACK VERSION <!-- New line separated list of affected versions, commit ID for issues on master branch. --> ~~~ 4.11.2, 4.13.0.0 tested ~~~ ##### CONFIGURATION <!-- Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise --> Xs and NFS or KVM and NFS/Ceph (have not tested VMware) ##### OS / ENVIRONMENT <!-- Information about the environment if relevant, N/A otherwise --> ##### SUMMARY <!-- Explain the problem/feature briefly --> When a snapshot is deleted (manually, or as part of the scheduled snap policy), snapshot is NOT deleted from Primary Storage (except KVM + Ceph, which is being fixed in https://github.com/apache/cloudstack/pull/3615) and is also NOT deleted from Secondary Storage. DB entries are inconsistent/partially cleared. ##### STEPS TO REPRODUCE <!-- For bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate. For new features, show how the feature would be used. --> XS+NFS tested as following Make snap (XS plus NFS), delete snap - snap is left on Primary Storage AND on Secondary Storage. Same goes for scheduled snap policy. "Primary" store ref row is deleted from the snapshots_store_ref but not really deleted on Primary Store. "image" store ref row is NOT deleted from snapshots_store_ref and image is NOT deleted on Secondary Store (after muiltiple runs of storage clean up thread i.e. storage.cleanup.delay=60, storage.cleanup.delay=60. KVM+Ceph tested as per the updates in https://github.com/apache/cloudstack/pull/3615 and will be tracker here. NOTE: XenserverSnapshotStrategy is NOT handling only XS, also some KVM Pay attention to the managed storage. This whole "garbage" problem was not there in 4.8 at least (possibly also 4.9). <!-- You can also paste gist.github.com links for larger files --> ##### EXPECTED RESULTS <!-- What did you expect to happen when running the steps above? --> ~~~ snapshot is deleted in both primary and secondary storage (after the cleanup thread runs) ~~~ ##### ACTUAL RESULTS <!-- What actually happened? --> <!-- Paste verbatim command output between quotes below --> ~~~ garbage is left, left and right ~~~
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
