Feature #3847

Cluster that are already imported should not be listed

Added by Carlos Martín over 5 years ago. Updated over 5 years ago.

Status:ClosedStart date:06/22/2015
Priority:NormalDue date:
Assignee:Tino Vázquez% Done:


Target version:Release 4.14
Resolution:fixed Pull request:


When vcenter resources are imported, the existing templates and vnets are filtered.
But all the clusters are returned, and a re-import of an existing cluster fails because of the already used name for the host.

Associated revisions

Revision 968730e4
Added by Tino Vázquez over 5 years ago

Feature #3847: Added check to avoid reimporting vCenter clusters

Added error handling


#1 Updated by Ruben S. Montero over 5 years ago

  • Assignee set to Tino Vázquez

#2 Updated by Tino Vázquez over 5 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100
  • Resolution set to fixed

Added check to avoid reimporting

Also available in: Atom PDF