New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

template delete recursive operation of templates instantiated as persistent does not remove images from the vcenter datastores #1350

OpenNebulaProject opened this Issue Nov 20, 2017 · 3 comments


None yet
6 participants
Copy link

OpenNebulaProject commented Nov 20, 2017

Author Name: Jaime Melis (@jmelis)
Original Redmine Issue: 5414,
Original Date: 2017-09-28

Steps to reproduce:

  • Instantiate a template (template0) as persistent
  • Teminate the vm
  • A new template (template1) is created, with a copy of the images from template0
  • Note the IMAGE/SOURCE of these new images
  • Delete template0 with --recursive option
  • The images have disappeared from opennebula, but they still exist in vCenter (in the IMAGE/SOURCE path)

The problem is due to the fact that the images have the tag TEMPLATE/VCENTER_IMPORTED = "YES", and datastore/vcenter/rm does not operate on them.


This comment has been minimized.

Copy link

ccesario commented Jul 6, 2018

I believe that this problem is the same reported in this post.
I have describe how to reproduce it


This comment has been minimized.

Copy link

Semedi commented Jul 20, 2018

VCENTER_IMPORTED is used to avoid rm operation on TM delete, this attribute shouldn't be copied in a clone operation (persistency) at core level.

Semedi added a commit to Semedi/one that referenced this issue Jul 25, 2018

@Semedi Semedi referenced this issue Sep 4, 2018


[vCenter] Improve TM Disk storage #2171

4 of 4 tasks complete

@Semedi Semedi modified the milestones: Release 5.6.1, Release 5.8 Sep 13, 2018


This comment has been minimized.

Copy link

Semedi commented Nov 23, 2018

should be solved in this issue #1762

@tinova tinova closed this Dec 21, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment