Bug #4942

Cannot import two vCenter datastores with the same name in different datacenters

Added by Miguel Ángel Álvarez Cabrerizo almost 4 years ago. Updated over 3 years ago.

Status:ClosedStart date:11/28/2016
Priority:NormalDue date:
Assignee:Miguel Ángel Álvarez Cabrerizo% Done:

0%

Category:vCenter
Target version:Release 5.4
Resolution: Pull request:
Affected Versions:OpenNebula 5.2

Description

The scope of a datastore is a datacenter; the datastore is uniquely named within the datacenter. If two datacenters have the same name for different datastores the import tool (onevcenter) will only give the chance to import the first one.

Selección_269.png (15.3 KB) Miguel Ángel Álvarez Cabrerizo, 04/02/2017 12:52 PM

History

#1 Updated by Miguel Ángel Álvarez Cabrerizo over 3 years ago

  • File Selección_268.png added
  • Status changed from New to Closed

Fixed in branch 4913, now when the import operation is called the name of the datastore has a prefix with the vcenter instance name followed by the datacenter name so the datastore allocation should not raise: Error creating datastore: [DatastoreAllocate] NAME is already taken by DATASTORE e.g: [10.0.1.140/Datacenter] nfs - Cluster (IMG)

See example in attached file

#2 Updated by Miguel Ángel Álvarez Cabrerizo over 3 years ago

  • File deleted (Selección_268.png)

#3 Updated by Miguel Ángel Álvarez Cabrerizo over 3 years ago

Correction. The name would be [ vcenter instance name - datacenter name ] datastore name - cluster name
e.g [10.0.1.140 - Datacenter] datastore1 - Cluster (SYS)

See imaged attached.

Also available in: Atom PDF